Run prebuild:ci and build

Author: benface

website/route-lockfile.txt

@@ -246,7 +246,8 @@
 /ar/supported-networks/xlayer-mainnet/
 /ar/supported-networks/xlayer-sepolia/
 /ar/supported-networks/zetachain/
-/ar/supported-networks/zilliqa-protomainnet/
+/ar/supported-networks/zilliqa-testnet/
+/ar/supported-networks/zilliqa/
 /ar/supported-networks/zksync-era-sepolia/
 /ar/supported-networks/zksync-era/
 /ar/supported-networks/zora/
@@ -520,7 +521,8 @@
 /cs/supported-networks/xlayer-mainnet/
 /cs/supported-networks/xlayer-sepolia/
 /cs/supported-networks/zetachain/
-/cs/supported-networks/zilliqa-protomainnet/
+/cs/supported-networks/zilliqa-testnet/
+/cs/supported-networks/zilliqa/
 /cs/supported-networks/zksync-era-sepolia/
 /cs/supported-networks/zksync-era/
 /cs/supported-networks/zora/
@@ -794,7 +796,8 @@
 /de/supported-networks/xlayer-mainnet/
 /de/supported-networks/xlayer-sepolia/
 /de/supported-networks/zetachain/
-/de/supported-networks/zilliqa-protomainnet/
+/de/supported-networks/zilliqa-testnet/
+/de/supported-networks/zilliqa/
 /de/supported-networks/zksync-era-sepolia/
 /de/supported-networks/zksync-era/
 /de/supported-networks/zora/
@@ -1068,7 +1071,8 @@
 /en/supported-networks/xlayer-mainnet/
 /en/supported-networks/xlayer-sepolia/
 /en/supported-networks/zetachain/
-/en/supported-networks/zilliqa-protomainnet/
+/en/supported-networks/zilliqa-testnet/
+/en/supported-networks/zilliqa/
 /en/supported-networks/zksync-era-sepolia/
 /en/supported-networks/zksync-era/
 /en/supported-networks/zora/
@@ -1342,7 +1346,8 @@
 /es/supported-networks/xlayer-mainnet/
 /es/supported-networks/xlayer-sepolia/
 /es/supported-networks/zetachain/
-/es/supported-networks/zilliqa-protomainnet/
+/es/supported-networks/zilliqa-testnet/
+/es/supported-networks/zilliqa/
 /es/supported-networks/zksync-era-sepolia/
 /es/supported-networks/zksync-era/
 /es/supported-networks/zora/
@@ -1616,7 +1621,8 @@
 /fr/supported-networks/xlayer-mainnet/
 /fr/supported-networks/xlayer-sepolia/
 /fr/supported-networks/zetachain/
-/fr/supported-networks/zilliqa-protomainnet/
+/fr/supported-networks/zilliqa-testnet/
+/fr/supported-networks/zilliqa/
 /fr/supported-networks/zksync-era-sepolia/
 /fr/supported-networks/zksync-era/
 /fr/supported-networks/zora/
@@ -1890,7 +1896,8 @@
 /hi/supported-networks/xlayer-mainnet/
 /hi/supported-networks/xlayer-sepolia/
 /hi/supported-networks/zetachain/
-/hi/supported-networks/zilliqa-protomainnet/
+/hi/supported-networks/zilliqa-testnet/
+/hi/supported-networks/zilliqa/
 /hi/supported-networks/zksync-era-sepolia/
 /hi/supported-networks/zksync-era/
 /hi/supported-networks/zora/
@@ -2164,7 +2171,8 @@
 /it/supported-networks/xlayer-mainnet/
 /it/supported-networks/xlayer-sepolia/
 /it/supported-networks/zetachain/
-/it/supported-networks/zilliqa-protomainnet/
+/it/supported-networks/zilliqa-testnet/
+/it/supported-networks/zilliqa/
 /it/supported-networks/zksync-era-sepolia/
 /it/supported-networks/zksync-era/
 /it/supported-networks/zora/
@@ -2438,7 +2446,8 @@
 /ja/supported-networks/xlayer-mainnet/
 /ja/supported-networks/xlayer-sepolia/
 /ja/supported-networks/zetachain/
-/ja/supported-networks/zilliqa-protomainnet/
+/ja/supported-networks/zilliqa-testnet/
+/ja/supported-networks/zilliqa/
 /ja/supported-networks/zksync-era-sepolia/
 /ja/supported-networks/zksync-era/
 /ja/supported-networks/zora/
@@ -2831,7 +2840,8 @@
 /mr/supported-networks/xlayer-mainnet/
 /mr/supported-networks/xlayer-sepolia/
 /mr/supported-networks/zetachain/
-/mr/supported-networks/zilliqa-protomainnet/
+/mr/supported-networks/zilliqa-testnet/
+/mr/supported-networks/zilliqa/
 /mr/supported-networks/zksync-era-sepolia/
 /mr/supported-networks/zksync-era/
 /mr/supported-networks/zora/
@@ -3343,7 +3353,8 @@
 /pt/supported-networks/xlayer-mainnet/
 /pt/supported-networks/xlayer-sepolia/
 /pt/supported-networks/zetachain/
-/pt/supported-networks/zilliqa-protomainnet/
+/pt/supported-networks/zilliqa-testnet/
+/pt/supported-networks/zilliqa/
 /pt/supported-networks/zksync-era-sepolia/
 /pt/supported-networks/zksync-era/
 /pt/supported-networks/zora/
@@ -3736,7 +3747,8 @@
 /ru/supported-networks/xlayer-mainnet/
 /ru/supported-networks/xlayer-sepolia/
 /ru/supported-networks/zetachain/
-/ru/supported-networks/zilliqa-protomainnet/
+/ru/supported-networks/zilliqa-testnet/
+/ru/supported-networks/zilliqa/
 /ru/supported-networks/zksync-era-sepolia/
 /ru/supported-networks/zksync-era/
 /ru/supported-networks/zora/
@@ -4010,7 +4022,8 @@
 /sv/supported-networks/xlayer-mainnet/
 /sv/supported-networks/xlayer-sepolia/
 /sv/supported-networks/zetachain/
-/sv/supported-networks/zilliqa-protomainnet/
+/sv/supported-networks/zilliqa-testnet/
+/sv/supported-networks/zilliqa/
 /sv/supported-networks/zksync-era-sepolia/
 /sv/supported-networks/zksync-era/
 /sv/supported-networks/zora/
@@ -4284,7 +4297,8 @@
 /tr/supported-networks/xlayer-mainnet/
 /tr/supported-networks/xlayer-sepolia/
 /tr/supported-networks/zetachain/
-/tr/supported-networks/zilliqa-protomainnet/
+/tr/supported-networks/zilliqa-testnet/
+/tr/supported-networks/zilliqa/
 /tr/supported-networks/zksync-era-sepolia/
 /tr/supported-networks/zksync-era/
 /tr/supported-networks/zora/
@@ -4677,7 +4691,8 @@
 /ur/supported-networks/xlayer-mainnet/
 /ur/supported-networks/xlayer-sepolia/
 /ur/supported-networks/zetachain/
-/ur/supported-networks/zilliqa-protomainnet/
+/ur/supported-networks/zilliqa-testnet/
+/ur/supported-networks/zilliqa/
 /ur/supported-networks/zksync-era-sepolia/
 /ur/supported-networks/zksync-era/
 /ur/supported-networks/zora/
@@ -4957,25 +4972,10 @@
 /zh/supported-networks/cronos/
 /zh/supported-networks/eos-evm/
 /zh/supported-networks/eos/
-/zh/supported-networks/etherlink-mainnet/
-/zh/supported-networks/etherlink-testnet/
-/zh/supported-networks/expchain-testnet/
-/zh/supported-networks/fantom-testnet/
-/zh/supported-networks/fantom/
-/zh/supported-networks/fraxtal/
 /zh/supported-networks/fuji/
-/zh/supported-networks/fuse/
-/zh/supported-networks/holesky-cl/
-/zh/supported-networks/holesky/
-/zh/supported-networks/hoodi-cl/
-/zh/supported-networks/hoodi/
 /zh/supported-networks/jungle4-evm/
 /zh/supported-networks/jungle4/
 /zh/supported-networks/kylin/
-/zh/supported-networks/mainnet-cl/
-/zh/supported-networks/mainnet/
-/zh/supported-networks/sepolia-cl/
-/zh/supported-networks/sepolia/
 /zh/token-api/evm/get-balances-evm-by-address/
 /zh/token-api/evm/get-historical-balances-evm-by-address/
 /zh/token-api/evm/get-holders-evm-by-contract/

website/src/openApi/tokenApi.json

@@ -3,16 +3,12 @@
   "info": {
     "title": "Token API (Beta)",
     "description": "Power your apps & AI agents with real-time token data.",
-    "version": "2.2.6+153a17c (2025-07-10)"
+    "version": "2.2.10+af1bb70 (2025-07-10)"
   },
   "servers": [
     {
-      "url": "https://token-api.thegraph.com",
-      "description": "Token API - Production"
-    },
-    {
-      "url": "http://localhost:8000",
-      "description": "Token API - Local"
+      "url": "https://token-api.thegraph.com/",
+      "description": "Token API - Remote"
     }
   ],
   "components": {
@@ -2165,7 +2161,7 @@
                           "datetime": {
                             "type": "string"
                           },
-                          "address": {
+                          "contract": {
                             "type": "string",
                             "description": "Filter by address"
                           },
@@ -2223,7 +2219,7 @@
                         "required": [
                           "block_num",
                           "datetime",
-                          "address",
+                          "contract",
                           "circulating_supply",
                           "holders",
                           "network_id",
@@ -2255,7 +2251,7 @@
                     {
                       "block_num": 22589353,
                       "datetime": "2025-05-29 15:40:11",
-                      "address": "0xc944e90c64b2c07662a292be6244bdf05cda44a7",
+                      "contract": "0xc944e90c64b2c07662a292be6244bdf05cda44a7",
                       "decimals": 18,
                       "symbol": "GRT",
                       "name": "Graph Token",
@@ -4222,8 +4218,8 @@
                   ]
                 },
                 "example": {
-                  "version": "2.2.6",
-                  "commit": "153a17c",
+                  "version": "2.2.10",
+                  "commit": "af1bb70",
                   "date": "2025-07-10",
                   "repo": "pinax-network/token-api"
                 }

website/src/pages/en/subgraphs/querying/graph-client/README.md

@@ -4,15 +4,15 @@ This repo is the home for [The Graph](https://thegraph.com) consumer-side tools
 
 ## Background
 
-The tools provided in this repo are intended to enrich and extend the DX, and add the additional layer required for dApps to implement distributed applications.
+The tools provided in this repo are intended to enrich and extend the DX, and add the additional layer required for dApps in order to implement distributed applications.
 
 Developers who consume data from [The Graph](https://thegraph.com) GraphQL API often need peripherals for making data consumption easier, and also tools that allow using multiple indexers at the same time.
 
 ## Features and Goals
 
 This library is intended to simplify the network aspect of data consumption for dApps. The tools provided within this repository are intended to run at build time, in order to make execution faster and performant at runtime.
 
-> The tools provided in this repo can be used as standalones, but you can also use them with any existing GraphQL Client!
+> The tools provided in this repo can be used as standalone, but you can also use it with any existing GraphQL Client!
 
 | Status | Feature                                                          | Notes                                                                                                                            |
 | :----: | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
@@ -67,7 +67,7 @@ graphclient build
 
 > Note: you need to run this with `yarn` prefix, or add that as a script in your `package.json`.
 
-This should produce a ready-to-use standalone `execute` function that you can use for running your application GraphQL operations. You should have an output similar to the following:
+This should produce a ready-to-use standalone `execute` function, that you can use for running your application GraphQL operations, you should have an output similar to the following:
 
 ```sh
 GraphClient: Cleaning existing artifacts
@@ -80,7 +80,7 @@ GraphClient: Reading the configuration
 🕸️: Done! => .graphclient
 ```
 
-Now that the `.graphclient` artifact is generated for you, you can import it directly from your code, and run your queries:
+Now, the `.graphclient` artifact is generated for you, and you can import it directly from your code, and run your queries:
 
 ```ts
 import { execute } from '../.graphclient'
@@ -449,7 +449,7 @@ sources:
         endpoint: https://api.thegraph.com/subgraphs/name/graphprotocol/compound-v2
 ```
 
-As long as there are no conflicts across the composed schemas, you can compose it, and then run a single query to both Subgraphs:
+As long as there a no conflicts across the composed schemas, you can compose it, and then run a single query to both Subgraphs:
 
 ```graphql
 query myQuery {
@@ -482,7 +482,7 @@ For advanced use-cases with composition, please refer to the following resources
 
 If your project is written in TypeScript, you can leverage the power of [`TypedDocumentNode`](https://the-guild.dev/blog/typed-document-node) and have a fully-typed GraphQL client experience.
 
-The standalone mode of The GraphQL, and popular GraphQL client libraries like Apollo-Client and urql have built-in support for `TypedDocumentNode`!
+The standalone mode of The GraphQL, and popular GraphQL client libraries like Apollo-Client and urql has built-in support for `TypedDocumentNode`!
 
 The Graph Client CLI comes with a ready-to-use configuration for [GraphQL Code Generator](https://graphql-code-generator.com), and it can generate `TypedDocumentNode` based on your GraphQL operations.
 
@@ -530,7 +530,7 @@ This is helpful since you can implement custom code as part of your GraphQL sche
 
 > This document explains how to add custom mutations, but in fact you can add any GraphQL operation (query/mutation/subscriptions). See [Extending the unified schema article](https://graphql-mesh.com/docs/guides/extending-unified-schema) for more information about this feature.
 
-To get started, define an `additionalTypeDefs` section in your config file:
+To get started, define a `additionalTypeDefs` section in your config file:
 
 ```yaml
 additionalTypeDefs: |

website/src/pages/en/subgraphs/querying/graph-client/architecture.md

@@ -5,7 +5,7 @@ To address the need to support a distributed network, we plan to take several ac
 1. Compose multiple Subgraphs (on the client-side)
 2. Fallback to multiple indexers/sources/hosted services
 3. Automatic/Manual source picking strategy
-4. Agnostic core, with the ability to integrate with any GraphQL client
+4. Agnostic core, with the ability to run integrate with any GraphQL client
 
 ## Standalone mode
 
@@ -44,7 +44,7 @@ graph LR;
 
 ## Subgraph Execution Strategies
 
-Within every Subgraph defined as source, there will be a way to define its source(s) indexer and the querying strategy, here are a few options:
+Within every Subgraph defined as source, there will be a way to define it's source(s) indexer and the querying strategy, here are a few options:
 
 ```mermaid
 graph LR;
@@ -85,7 +85,7 @@ graph LR;
     end
 ```
 
-> We can ship several built-in strategies, along with a simple interface to allow developers to write their own.
+> We can ship a several built-in strategies, along with a simple interfaces to allow developers to write their own.
 
 To take the concept of strategies to the extreme, we can even build a magical layer that does subscription-as-query, with any hook, and provide a smooth DX for dapps:
 

website/src/pages/en/subgraphs/querying/graph-client/live.md

@@ -38,6 +38,6 @@ query ExampleQuery @live(interval: 5000) {
 
 ## Integrations
 
-Since the entire network layer (along with the `@live` mechanism) is implemented inside `graph-client` core, you can use Live queries with every GraphQL client (such as Urql or Apollo-Client), as long as it supports streamed responses (`AsyncIterable`).
+Since the entire network layer (along with the `@live` mechanism) is implemented inside `graph-client` core, you can use Live queries with every GraphQL client (such as Urql or Apollo-Client), as long as it supports streame responses (`AsyncIterable`).
 
 No additional setup is required for GraphQL clients cache updates.