fix links

rtso · rtso · commit 0b1cda1a8078 · 2025-01-30T13:57:08.000-05:00
diff --git a/apps/nextra/pages/en/build/apis/fullnode-rest-api.mdx b/apps/nextra/pages/en/build/apis/fullnode-rest-api.mdx
@@ -29,7 +29,7 @@ For more advanced queries, we recommend using the [Indexer GraphQL API](../index
 
 ## Understanding rate limits
 
-As with the [Aptos Indexer](../indexer/aptos-hosted.mdx), the Aptos REST API has a rate limit of 5000
+As with the [Aptos Indexer](../indexer/indexer-api.mdx), the Aptos REST API has a rate limit of 5000
 requests per five minutes by IP address, whether submitting transactions or querying the API on Aptos-provided nodes.
 (As a node operator, you may raise those limits on your own node.) Note that this limit can change with or without prior
 notice.
diff --git a/apps/nextra/pages/en/build/cli/running-a-local-network.mdx b/apps/nextra/pages/en/build/cli/running-a-local-network.mdx
@@ -117,7 +117,7 @@ To debug this, try the below fixes:
 As you can see from the example output in step 4, once the local network is running, you have access to the following services:
 
 - [Node API](../../network/nodes/aptos-api-spec.mdx): This is a REST API that runs directly on the node. It enables core write functionality such as transaction submission and a limited set of read functionality, such as reading account resources or Move module information.
-- [Indexer API](../indexer/aptos-hosted.mdx): This is a [GraphQL](https://graphql.org/) API that provides rich read access to indexed blockchain data. If you click on the URL for the Indexer API above, by default [http://127.0.0.1:8090](http://127.0.0.1:8090/), it will open the Hasura Console, a web UI that will help you query the Indexer GraphQL API.
+- [Indexer API](../indexer/indexer-api.mdx): This is a [GraphQL](https://graphql.org/) API that provides rich read access to indexed blockchain data. If you click on the URL for the Indexer API above, by default [http://127.0.0.1:8090](http://127.0.0.1:8090/), it will open the Hasura Console, a web UI that will help you query the Indexer GraphQL API.
 - [Transaction Stream Service](../indexer/txn-stream.mdx): This is a gRPC stream of transactions used by the Indexer API and SDK. This is only relevant to you if you are developing a [Indexer SDK](../indexer/indexer-sdk.mdx) custom processor.
 - [Postgres](https://www.postgresql.org/): This is the database that the Indexer processors write to. The Indexer API reads from this database.
 - [Faucet](../apis/faucet-api.mdx): You can use this to fund accounts on your local network.
diff --git a/apps/nextra/pages/en/build/get-started.mdx b/apps/nextra/pages/en/build/get-started.mdx
@@ -40,7 +40,7 @@ import { Cards, Card, GraphQLEditor } from '@components/index';
   </Card>
 </Cards>
 
-Here's an interactive example of our [Indexer](indexer.mdx) and how you can query for the Current Fungible Asset Balances of an account. More usage examples can be found in [example queries](indexer/fungible-asset-balances.mdx).
+Here's an interactive example of our [Indexer](indexer.mdx) and how you can query for the Current Fungible Asset Balances of an account. More usage examples can be found in [example queries](indexer/indexer-api/fungible-asset-balances.mdx).
 
 <GraphQLEditor
   query={`query GetFungibleAssetBalances($address: String, $offset: Int) {
diff --git a/apps/nextra/pages/en/build/indexer.mdx b/apps/nextra/pages/en/build/indexer.mdx
@@ -50,19 +50,19 @@ The Indexer tracks every transaction that happens on-chain, then exposes that da
 Learn how to use the Indexer API, what each table represents, and the architecture.
 
 <Cards>
-  <Card href="indexer/aptos-hosted">
+  <Card href="indexer/indexer-api">
     <Card.Title>Accessing the API</Card.Title>
     <Card.Description>Learn how to query the Indexer API.</Card.Description>
   </Card>
-    <Card href="indexer/indexer-reference">
+    <Card href="indexer/indexer-api/indexer-reference">
     <Card.Title>Indexer Table Reference</Card.Title>
     <Card.Description>Detailed reference for Indexer tables and their schemas.</Card.Description>
   </Card>
-  <Card href="indexer/architecture">
+  <Card href="indexer/indexer-api/architecture">
     <Card.Title>Architecture</Card.Title>
     <Card.Description>Detailed layout of the Indexer's architecture.</Card.Description>
   </Card>
-    <Card href="indexer/self-hosted">
+    <Card href="indexer/indexer-api/self-hosted">
     <Card.Title>Self-hosted Indexer API</Card.Title>
     <Card.Description>Host your own Indexer API</Card.Description>
   </Card>
@@ -73,35 +73,35 @@ Learn how to use the Indexer API, what each table represents, and the architectu
 To help get you started, here are the most common queries the Indexer is used for.
 
 <Cards>
-  <Card href="indexer/fungible-asset-balances">
+  <Card href="indexer/indexer-api/fungible-asset-balances">
     <Card.Title>Get Fungible Asset Balances</Card.Title>
     <Card.Description>Get all fungible assets an account currently owns.</Card.Description>
   </Card>
-  <Card href="indexer/account-transactions">
+  <Card href="indexer/indexer-api/account-transactions">
     <Card.Title>Get Account Transactions</Card.Title>
     <Card.Description>Get all transactions impacting an account.</Card.Description>
   </Card>
-  <Card href="indexer/ans-lookup">
+  <Card href="indexer/indexer-api/ans-lookup">
     <Card.Title>Get Aptos Name</Card.Title>
     <Card.Description>Retrieve the Aptos name associated with an account (via the ANS).</Card.Description>
   </Card>
-  <Card href="indexer/fungible-asset-info">
+  <Card href="indexer/indexer-api/fungible-asset-info">
     <Card.Title>Get Fungible Asset Info</Card.Title>
     <Card.Description>Get detailed information about a specific fungible asset.</Card.Description>
   </Card>
-  <Card href="indexer/get-nft-collections">
+  <Card href="indexer/indexer-api/get-nft-collections">
     <Card.Title>Get NFT Collections</Card.Title>
     <Card.Description>Retrieve NFT collections owned by a specific account.</Card.Description>
   </Card>
-  <Card href="indexer/get-nfts">
+  <Card href="indexer/indexer-api/get-nfts">
     <Card.Title>Get NFTs</Card.Title>
     <Card.Description>Retrieve individual NFTs owned by a specific account.</Card.Description>
   </Card>
-  <Card href="indexer/token-metadata">
+  <Card href="indexer/indexer-api/token-metadata">
     <Card.Title>Get Token Metadata</Card.Title>
     <Card.Description>Get metadata information for a specific token.</Card.Description>
   </Card>
-  <Card href="indexer/get-delegators">
+  <Card href="indexer/indexer-api/get-delegators">
     <Card.Title>Count Delegators in Staking Pool</Card.Title>
     <Card.Description>Retrieve the number of active delegators in a staking pool.</Card.Description>
   </Card>
@@ -112,11 +112,11 @@ To help get you started, here are the most common queries the Indexer is used fo
 If the hosted Indexer API is not enough or if you want to index your custom contract, you can create a processor with the [Indexer SDK](./indexer/indexer-sdk.mdx).
 
 <Cards>
-  <Card href="indexer-sdk/quickstart">
+  <Card href="indexer/indexer-sdk/quickstart">
     <Card.Title>Quickstart Guide</Card.Title>
     <Card.Description>Get started with the Indexer SDK</Card.Description>
   </Card>
-  <Card href="indexer-sdk/documentation">
+  <Card href="indexer/indexer-sdk/documentation">
     <Card.Title>Documentation</Card.Title>
     <Card.Description>Read documentation about the Indexer SDK</Card.Description>
   </Card>
diff --git a/apps/nextra/pages/en/build/indexer/indexer-api.mdx b/apps/nextra/pages/en/build/indexer/indexer-api.mdx
@@ -13,7 +13,7 @@ Aptos Labs hosts a public version of the Indexer GraphQL API that anyone can use
 
 You can explore it by hand by viewing the Hasura Explorer below for the network you are interested in.
 
-You can also access the API via the GraphQL endpoints below. For more information on the format of data in each field / table, please see the [table reference page](indexer-reference.mdx).
+You can also access the API via the GraphQL endpoints below. For more information on the format of data in each field / table, please see the [table reference page](./indexer-api/indexer-reference.mdx).
 
 ## SDK Access (Primary Method)
 
@@ -61,5 +61,5 @@ The following rate limit applies for the Aptos Labs hosted indexer API:
 If you need a higher rate limit, consider the following solutions:
 
 1. Get an API Key from [API Gateway](https://developers.aptoslabs.com/).
-2. Run the Aptos Indexer API yourself. See the guide to self-hosting [here](self-hosted.mdx).
+2. Run the Aptos Indexer API yourself. See the guide to self-hosting [here](./txn-stream/self-hosted.mdx).
 
diff --git a/apps/nextra/pages/en/build/indexer/indexer-api/architecture.mdx b/apps/nextra/pages/en/build/indexer/indexer-api/architecture.mdx
@@ -29,9 +29,9 @@ Here is how the Indexer creates that API at a high-level:
   />
 </center>
 
-The Indexer uses the [Transaction Stream Service](./txn-stream.mdx) and custom processors written with the [Indexer SDK](./indexer-sdk.mdx) to update a database with rich tables. Then it exposes an API for Aptos apps to access the consolidated data.
+The Indexer uses the [Transaction Stream Service](../txn-stream.mdx) and custom processors written with the [Indexer SDK](../indexer-sdk.mdx) to update a database with rich tables. Then it exposes an API for Aptos apps to access the consolidated data.
 
-For situations where you need to go beyond the Aptos hosted Indexer API data, you will want to create a custom processor with the Indexer SDK (./indexer-sdk.mdx).
+For situations where you need to go beyond the Aptos hosted Indexer API data, you will want to create a custom processor with the [Indexer SDK](../indexer-sdk.mdx).
 
 Writing a custom processor can help you:
 1. Get access to different types of data.
diff --git a/apps/nextra/pages/en/build/indexer/indexer-api/indexer-reference.mdx b/apps/nextra/pages/en/build/indexer/indexer-api/indexer-reference.mdx
@@ -8,7 +8,7 @@ import { Card, Cards } from '@components/index';
 
 # Indexer API Reference
 
-The Indexer API allows you to access rich data about tokens, accounts, transactions, and events on-chain using GraphQL queries. **You can access it [here](./aptos-hosted.mdx).**
+The Indexer API allows you to access rich data about tokens, accounts, transactions, and events on-chain using GraphQL queries. **You can access it [here](../indexer-api.mdx).**
 
 For common queries, check out the sidebar for examples to work from. When building your own, this reference guide should help you determine which tables are most relevant, and how to format your queries.
 
@@ -24,7 +24,7 @@ If you are looking up a table with the `_by_pk` suffix, search for the table nam
 # Indexer Table Reference
 
 <Callout type="info">
-Remember to use Ctrl + F to find the table you are interested in! When in doubt, you may also want to query the Hasura tables linked in the [Indexer API Access](./aptos-hosted.mdx) page to see examples of the data inside.
+Remember to use Ctrl + F to find the table you are interested in! When in doubt, you may also want to query the Hasura tables linked in the [Indexer API Access](../indexer-api.mdx) page to see examples of the data inside.
 </Callout>
 
 ## Raw Data
@@ -261,7 +261,7 @@ This tracks the activity of fungible assets. It includes v1 token data.
 | metadata                    | Object  |             | Use the [Hasura explorer](https://cloud.hasura.io/public/graphiql?endpoint=https://api.mainnet.aptoslabs.com/v1/graphql) to see fields for `metadata` in this table.                                                        |
 | owner_address               | String  |             | This is an Aptos account address that owns the asset. Addresses must be 66 characters long, and so may be 0 padded. Ex. "0xa815a9a09105973084bfc31530e7c8f002846787c2f0521e1e34dc144ad83b89" |
 | storage_id                  | String  |             | Identifier for the storage used in the transaction. IDs must be 66 characters long, and so may be 0 padded. Ex. "0xa815a9a09105973084bfc31530e7c8f002846787c2f0521e1e34dc144ad83b89" |
-| storage_refund_amount       | bigint  |             | Amount refunded for storage after the transaction. This is always in APT [octas](../../network/glossary.mdx#Octa). Ex. 50                                                                |
+| storage_refund_amount       | bigint  |             | Amount refunded for storage after the transaction. This is always in APT [octas](../../../network/glossary.mdx#Octa). Ex. 50                                                                |
 | token_standard              | String  |             | Aptos standard that the collection adheres to. Ex. "v1"                                                                                              |
 | transaction_timestamp       | String  |             | Timestamp when the transaction occurred. Ex. "2024-04-17T02:14:25.68771"                                                                             |
 | transaction_version         | bigint  |             | Blockchain version of the transaction. Ex. 2                                                                                                         |
diff --git a/apps/nextra/pages/en/build/indexer/indexer-api/self-hosted.mdx b/apps/nextra/pages/en/build/indexer/indexer-api/self-hosted.mdx
@@ -60,11 +60,11 @@ If you're running this from a Docker Desktop environment (which you likely are i
 
 ### `indexer_grpc_data_service_address`
 
-This is the URL for the Transaction Stream Service. If you are using the Labs-Hosted instance you can find the URLs for each network at [this page](aptos-hosted.mdx). Make sure to select the correct URL for the network you want to index. If you are running this service locally the value should be `127.0.0.1:50051`.
+This is the URL for the Transaction Stream Service. If you are using the Labs-Hosted instance you can find the URLs for each network at [this page](../indexer-api.mdx). Make sure to select the correct URL for the network you want to index. If you are running this service locally the value should be `127.0.0.1:50051`.
 
 ### `auth_token`
 
-This is the auth token used to connect to the Transaction Stream Service. If you are using the Labs-Hosted instance you can use the API Gateway to get an API key. Learn more at [this page](aptos-hosted.mdx).
+This is the auth token used to connect to the Transaction Stream Service. If you are using the Labs-Hosted instance you can use the API Gateway to get an API key. Learn more at [this page](../indexer-api.mdx).
 
 ## Run with source code
 
diff --git a/apps/nextra/pages/en/build/indexer/indexer-sdk.mdx b/apps/nextra/pages/en/build/indexer/indexer-sdk.mdx
@@ -24,10 +24,6 @@ Learn how to use the Indexer SDK through guides and documentation.
     <Card.Title>Documentation</Card.Title>
     <Card.Description>Read documentation about the Indexer SDK</Card.Description>
   </Card>
-  <Card href="indexer-sdk/advanced-tutorials">
-    <Card.Title>Advanced Tutorials</Card.Title>
-    <Card.Description>Learn advanced topics about the Indexer SDK</Card.Description>
-  </Card>
 </Cards>
 
 
diff --git a/apps/nextra/pages/en/build/indexer/indexer-sdk/documentation.mdx b/apps/nextra/pages/en/build/indexer/indexer-sdk/documentation.mdx
@@ -30,7 +30,7 @@ Each `Step` has an input and output, and the output of each `Step` is connected
 </center>
 
 ## When to use the Indexer SDK
-The Indexer SDK is useful when you want to index a custom contract or you realize you need a new kind of data that isn't available in the [Indexer API](../aptos-hosted.mdx).
+The Indexer SDK is useful when you want to index a custom contract or you realize you need a new kind of data that isn't available in the [Indexer API](../indexer-api.mdx).
 
 The general flow to write a custom processor with the Indexer SDK is:
 1. Define your database schema
diff --git a/apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/create-processor.mdx b/apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/create-processor.mdx
@@ -102,7 +102,7 @@ loop {
 ```
 
 You can see a full example of a processor that indexes raw Aptos events in [`aptos-indexer-processor-example`](https://github.com/aptos-labs/aptos-indexer-processor-example/blob/main/aptos-indexer-processor-example/src/processors/events/events_processor.rs). 
-As a reference, you can also see all of the processors that make up the [Indexer API](../../aptos-hosted.mdx) in [`aptos-indexer-processors`](https://github.com/aptos-labs/aptos-indexer-processors/tree/main/rust/sdk-processor/src/processors).
+As a reference, you can also see all of the processors that make up the [Indexer API](../../indexer-api.mdx) in [`aptos-indexer-processors`](https://github.com/aptos-labs/aptos-indexer-processors/tree/main/rust/sdk-processor/src/processors).
 
 ## How to define `main.rs`
 You may copy the [`main.rs`](https://github.com/aptos-labs/aptos-indexer-processor-example/blob/main/aptos-indexer-processor-example/src/main.rs) file from the `aptos-indexer-processor-example`. 
diff --git a/apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/define-schema.mdx b/apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/define-schema.mdx
@@ -15,7 +15,7 @@ Ensure your schema is customized to meet your dApp's unique requirements.
 By using the indexer, a single indexer query can often replace multiple queries to the fullnode.
 
 ## Aptos Core Processors
-All data exposed by the [Indexer API](../../aptos-hosted.mdx) is initially indexed using custom processors.
+All data exposed by the [Indexer API](../../indexer-api.mdx) is initially indexed using custom processors.
 Each core processor indexes a specific type of data.
 You can explore the [full list of processors](https://github.com/aptos-labs/aptos-indexer-processors/tree/main/rust/sdk-processor/src/processors) and the [complete indexer data schema](https://github.com/aptos-labs/aptos-indexer-processors/blob/main/rust/processor/src/db/postgres/schema.rs).
 
diff --git a/apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/steps.mdx b/apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/steps.mdx
@@ -107,6 +107,6 @@ The SDK comes with a set of [common steps](https://github.com/aptos-labs/aptos-i
 
 1. `TransactionStreamStep` provides a stream of Aptos transactions to the processor. Read more about it [here](./steps/transaction-stream.mdx).
 2. `TimedBufferStep` buffers a batch of items and periodically polls to release the items to the next step
-3. `VersionTrackerStep` tracks the progress of the processor and checkpoints the processor's progress. Read more about it [here](../version-tracking.mdx).
+3. `VersionTrackerStep` tracks the progress of the processor and checkpoints the processor's progress. Read more about it [here](./version-tracking.mdx).
 4. `OrderByVersionStep` orders transaction contextx by their starting versions. It buffers ordered these contexts and releases them at every poll interval.
 5. `WriteRateLimitStep` limits the number of bytes written to the database per second.
diff --git a/apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/steps/parsing-txns.mdx b/apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/steps/parsing-txns.mdx
@@ -17,7 +17,7 @@ Fundamentally an indexer processor is just something that consumes a stream of a
 
 ## What is a transaction?
 
-A transaction is a unit of execution on the Aptos blockchain. If the execution of the program in a transaction (e.g. starting with an entry function in a Move module) is successful, the resulting change in state will be applied to the ledger. Learn more about the transaction lifecycle at [this page](../../../../network/blockchain/blockchain-deep-dive.mdx#life-of-a-transaction).
+A transaction is a unit of execution on the Aptos blockchain. If the execution of the program in a transaction (e.g. starting with an entry function in a Move module) is successful, the resulting change in state will be applied to the ledger. Learn more about the transaction lifecycle at [this page](../../../../../network/blockchain/blockchain-deep-dive.mdx#life-of-a-transaction).
 
 There are four types of transactions on Aptos:
 
@@ -28,7 +28,7 @@ There are four types of transactions on Aptos:
 
 The first 3 of these are internal to the system and are not relevant to most processors; we do not cover them in this guide.
 
-Generally speaking, most user transactions originate from a user calling an entry function in a Move module deployed on chain, for example `0x1::coin::transfer`. In all other cases they originate from [Move scripts](../../../smart-contracts/scripts.mdx). You can learn more about the different types of transactions [here](../../../../network/blockchain/txns-states.mdx#types-of-transaction-payloads).
+Generally speaking, most user transactions originate from a user calling an entry function in a Move module deployed on chain, for example `0x1::coin::transfer`. In all other cases they originate from [Move scripts](../../../../smart-contracts/scripts.mdx). You can learn more about the different types of transactions [here](../../../../../network/blockchain/txns-states.mdx#types-of-transaction-payloads).
 
 A user transaction that a processor handles contains a variety of information. At a high level it contains:
 
@@ -47,7 +47,7 @@ The payload is what the user submits to the blockchain when they wish to execute
 - The address + module name + function name of the function being executed.
 - The arguments to the function.
 
-There is other potentially interesting information in the payload that you can learn about at [this page](../../../../network/blockchain/txns-states.mdx#contents-of-a-transaction).
+There is other potentially interesting information in the payload that you can learn about at [this page](../../../../../network/blockchain/txns-states.mdx#contents-of-a-transaction).
 
 ### Events
 
diff --git a/apps/nextra/pages/en/build/indexer/legacy/migration.mdx b/apps/nextra/pages/en/build/indexer/legacy/migration.mdx
diff --git a/apps/nextra/pages/en/build/indexer/txn-stream/aptos-hosted-txn-stream.mdx b/apps/nextra/pages/en/build/indexer/txn-stream/aptos-hosted-txn-stream.mdx
diff --git a/apps/nextra/pages/en/build/smart-contracts/digital-asset.mdx b/apps/nextra/pages/en/build/smart-contracts/digital-asset.mdx
diff --git a/apps/nextra/pages/en/network/nodes/localnet/local-development-network.mdx b/apps/nextra/pages/en/network/nodes/localnet/local-development-network.mdx
diff --git a/apps/nextra/pages/zh/build/apis/fullnode-rest-api.mdx b/apps/nextra/pages/zh/build/apis/fullnode-rest-api.mdx
diff --git a/apps/nextra/pages/zh/build/cli/running-a-local-network.mdx b/apps/nextra/pages/zh/build/cli/running-a-local-network.mdx
diff --git a/apps/nextra/pages/zh/network/nodes/localnet/local-development-network.mdx b/apps/nextra/pages/zh/network/nodes/localnet/local-development-network.mdx
