Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
63 changes: 63 additions & 0 deletions docs/HyperIndex/supported-networks/chainweb-testnet-20.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
id: chainweb-testnet-20
title: Chainweb Testnet 20
sidebar_label: Chainweb Testnet 20
slug: /chainweb-testnet-20
---

# Chainweb Testnet 20

## Indexing Chainweb Testnet 20 Data with Envio

| **Field** | **Value** |
|-------------------------------|----------------------------------------------------------------------------------------------------|
| **Chainweb Testnet 20 Chain ID** | 5920 |
| **HyperSync URL Endpoint** | [https://chainweb-testnet-20.hypersync.xyz](https://chainweb-testnet-20.hypersync.xyz) or [https://5920.hypersync.xyz](https://5920.hypersync.xyz) |
| **HyperRPC URL Endpoint** | [https://chainweb-testnet-20.rpc.hypersync.xyz](https://chainweb-testnet-20.rpc.hypersync.xyz) or [https://5920.rpc.hypersync.xyz](https://5920.rpc.hypersync.xyz) |

---

### Tier

STONE 🪨

### Overview

Envio is a modular hyper-performant data indexing solution for Chainweb Testnet 20, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC).

HyperSync accelerates the synchronization of historical data on Chainweb Testnet 20, enabling what usually takes hours to sync millions of events to be completed in under a minute—up to 1000x faster than traditional RPC methods.

Designed to optimize the user experience, Envio offers automatic code generation, flexible language support, multi-chain data aggregation, and a reliable, cost-effective hosted service.

To get started, see our documentation or follow our quickstart [guide](/docs/HyperIndex/contract-import).

---

### Defining Network Configurations

```yaml
name: IndexerName # Specify indexer name
description: Indexer Description # Include indexer description
networks:
- id: 5920 # Chainweb Testnet 20
start_block: START_BLOCK_NUMBER # Specify the starting block
contracts:
- name: ContractName
address:
- "0xYourContractAddress1"
- "0xYourContractAddress2"
handler: ./src/EventHandlers.ts
events:
- event: Event # Specify event
- event: Event
```
Comment on lines +38 to +53
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Same indentation bug in YAML snippet

The address list items need two more spaces:

-        address:
-         - "0xYourContractAddress1"
-         - "0xYourContractAddress2"
+        address:
+          - "0xYourContractAddress1"
+          - "0xYourContractAddress2"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
```yaml
name: IndexerName # Specify indexer name
description: Indexer Description # Include indexer description
networks:
- id: 5920 # Chainweb Testnet 20
start_block: START_BLOCK_NUMBER # Specify the starting block
contracts:
- name: ContractName
address:
- "0xYourContractAddress1"
- "0xYourContractAddress2"
handler: ./src/EventHandlers.ts
events:
- event: Event # Specify event
- event: Event
```
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/chainweb-testnet-20.md between lines 38
and 53, the YAML snippet has incorrect indentation for the address list items
under contracts. The list items under address should be indented two more spaces
to align properly with YAML syntax. Adjust the indentation of the address
entries so they are correctly nested under the address key.


With these steps completed, your application will be set to efficiently index Chainweb Testnet 20 data using Envio’s blockchain indexer.

For more information on how to set up your config, define a schema, and write event handlers, refer to the guides section in our [documentation](/docs/HyperIndex/configuration-file).

### Support

Can’t find what you’re looking for or need support? Reach out to us on [Discord](https://discord.com/invite/Q9qt8gZ2fX); we’re always happy to help!

---
63 changes: 63 additions & 0 deletions docs/HyperIndex/supported-networks/chainweb-testnet-21.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
id: chainweb-testnet-21
title: Chainweb Testnet 21
sidebar_label: Chainweb Testnet 21
slug: /chainweb-testnet-21
---

# Chainweb Testnet 21

## Indexing Chainweb Testnet 21 Data with Envio

| **Field** | **Value** |
|-------------------------------|----------------------------------------------------------------------------------------------------|
| **Chainweb Testnet 21 Chain ID** | 5921 |
| **HyperSync URL Endpoint** | [https://chainweb-testnet-21.hypersync.xyz](https://chainweb-testnet-21.hypersync.xyz) or [https://5921.hypersync.xyz](https://5921.hypersync.xyz) |
| **HyperRPC URL Endpoint** | [https://chainweb-testnet-21.rpc.hypersync.xyz](https://chainweb-testnet-21.rpc.hypersync.xyz) or [https://5921.rpc.hypersync.xyz](https://5921.rpc.hypersync.xyz) |

---

### Tier

STONE 🪨

### Overview

Envio is a modular hyper-performant data indexing solution for Chainweb Testnet 21, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC).

HyperSync accelerates the synchronization of historical data on Chainweb Testnet 21, enabling what usually takes hours to sync millions of events to be completed in under a minute—up to 1000x faster than traditional RPC methods.

Designed to optimize the user experience, Envio offers automatic code generation, flexible language support, multi-chain data aggregation, and a reliable, cost-effective hosted service.

To get started, see our documentation or follow our quickstart [guide](/docs/HyperIndex/contract-import).

---

### Defining Network Configurations

```yaml
name: IndexerName # Specify indexer name
description: Indexer Description # Include indexer description
networks:
- id: 5921 # Chainweb Testnet 21
start_block: START_BLOCK_NUMBER # Specify the starting block
contracts:
- name: ContractName
address:
- "0xYourContractAddress1"
- "0xYourContractAddress2"
handler: ./src/EventHandlers.ts
events:
- event: Event # Specify event
- event: Event
```
Comment on lines +38 to +53
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

YAML indentation is off – the sample won’t parse as-is

The list items under address: need two additional spaces to be a child of the scalar. Current indentation yields a top-level list and breaks the schema.
Proposed fix:

-        address:
-         - "0xYourContractAddress1"
-         - "0xYourContractAddress2"
+        address:
+          - "0xYourContractAddress1"
+          - "0xYourContractAddress2"
🤖 Prompt for AI Agents
In docs/HyperIndex/supported-networks/chainweb-testnet-21.md around lines 38 to
53, the YAML indentation for the list under the address key is incorrect,
causing parsing errors. Fix this by indenting the address list items two spaces
further so they are properly nested as children of the address key, ensuring
valid YAML structure.


With these steps completed, your application will be set to efficiently index Chainweb Testnet 21 data using Envio’s blockchain indexer.

For more information on how to set up your config, define a schema, and write event handlers, refer to the guides section in our [documentation](/docs/HyperIndex/configuration-file).

### Support

Can’t find what you’re looking for or need support? Reach out to us on [Discord](https://discord.com/invite/Q9qt8gZ2fX); we’re always happy to help!

---
63 changes: 63 additions & 0 deletions docs/HyperIndex/supported-networks/plume.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
id: plume
title: Plume
sidebar_label: Plume
slug: /plume
---

# Plume

## Indexing Plume Data with Envio

| **Field** | **Value** |
|-------------------------------|----------------------------------------------------------------------------------------------------|
| **Plume Chain ID** | 98866 |
| **HyperSync URL Endpoint** | [https://plume.hypersync.xyz](https://plume.hypersync.xyz) or [https://98866.hypersync.xyz](https://98866.hypersync.xyz) |
| **HyperRPC URL Endpoint** | [https://plume.rpc.hypersync.xyz](https://plume.rpc.hypersync.xyz) or [https://98866.rpc.hypersync.xyz](https://98866.rpc.hypersync.xyz) |

---

### Tier

STONE 🪨

### Overview

Envio is a modular hyper-performant data indexing solution for Plume, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC).

HyperSync accelerates the synchronization of historical data on Plume, enabling what usually takes hours to sync millions of events to be completed in under a minute—up to 1000x faster than traditional RPC methods.

Designed to optimize the user experience, Envio offers automatic code generation, flexible language support, multi-chain data aggregation, and a reliable, cost-effective hosted service.

To get started, see our documentation or follow our quickstart [guide](/docs/HyperIndex/contract-import).

---

### Defining Network Configurations

```yaml
name: IndexerName # Specify indexer name
description: Indexer Description # Include indexer description
networks:
- id: 98866 # Plume
start_block: START_BLOCK_NUMBER # Specify the starting block
contracts:
- name: ContractName
address:
- "0xYourContractAddress1"
- "0xYourContractAddress2"
handler: ./src/EventHandlers.ts
events:
- event: Event # Specify event
- event: Event
```

With these steps completed, your application will be set to efficiently index Plume data using Envio’s blockchain indexer.

For more information on how to set up your config, define a schema, and write event handlers, refer to the guides section in our [documentation](/docs/HyperIndex/configuration-file).

### Support

Can’t find what you’re looking for or need support? Reach out to us on [Discord](https://discord.com/invite/Q9qt8gZ2fX); we’re always happy to help!

---
2 changes: 1 addition & 1 deletion docs/HyperIndex/supported-networks/tangle.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ slug: /tangle

### Tier

BRONZE 🥉
STONE 🪨

### Overview

Expand Down
63 changes: 63 additions & 0 deletions docs/HyperIndex/supported-networks/taraxa.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
id: taraxa
title: Taraxa
sidebar_label: Taraxa
slug: /taraxa
---

# Taraxa

## Indexing Taraxa Data with Envio

| **Field** | **Value** |
|-------------------------------|----------------------------------------------------------------------------------------------------|
| **Taraxa Chain ID** | 841 |
| **HyperSync URL Endpoint** | [https://taraxa.hypersync.xyz](https://taraxa.hypersync.xyz) or [https://841.hypersync.xyz](https://841.hypersync.xyz) |
| **HyperRPC URL Endpoint** | [https://taraxa.rpc.hypersync.xyz](https://taraxa.rpc.hypersync.xyz) or [https://841.rpc.hypersync.xyz](https://841.rpc.hypersync.xyz) |

---

### Tier

BRONZE 🥉

### Overview

Envio is a modular hyper-performant data indexing solution for Taraxa, enabling applications and developers to efficiently index and aggregate real-time and historical blockchain data. Envio offers three primary solutions for indexing and accessing large amounts of data: [HyperIndex](/docs/HyperIndex/overview) (a customizable indexing framework), [HyperSync](/docs/HyperSync/overview) (a real-time indexed data layer), and [HyperRPC](/docs/HyperSync/overview-hyperrpc) (extremely fast read-only RPC).

HyperSync accelerates the synchronization of historical data on Taraxa, enabling what usually takes hours to sync millions of events to be completed in under a minute—up to 1000x faster than traditional RPC methods.

Designed to optimize the user experience, Envio offers automatic code generation, flexible language support, multi-chain data aggregation, and a reliable, cost-effective hosted service.

To get started, see our documentation or follow our quickstart [guide](/docs/HyperIndex/contract-import).

---

### Defining Network Configurations

```yaml
name: IndexerName # Specify indexer name
description: Indexer Description # Include indexer description
networks:
- id: 841 # Taraxa
start_block: START_BLOCK_NUMBER # Specify the starting block
contracts:
- name: ContractName
address:
- "0xYourContractAddress1"
- "0xYourContractAddress2"
handler: ./src/EventHandlers.ts
events:
- event: Event # Specify event
- event: Event
```

With these steps completed, your application will be set to efficiently index Taraxa data using Envio’s blockchain indexer.

For more information on how to set up your config, define a schema, and write event handlers, refer to the guides section in our [documentation](/docs/HyperIndex/configuration-file).

### Support

Can’t find what you’re looking for or need support? Reach out to us on [Discord](https://discord.com/invite/Q9qt8gZ2fX); we’re always happy to help!

---
7 changes: 5 additions & 2 deletions docs/HyperSync/HyperRPC/hyperrpc-url-endpoints.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,8 @@ Here is a table of the currently supported networks on HyperRPC and their respec
| Bsc | 56 | https://bsc.rpc.hypersync.xyz or https://56.rpc.hypersync.xyz | |
| Bsc Testnet | 97 | https://bsc-testnet.rpc.hypersync.xyz or https://97.rpc.hypersync.xyz | |
| Celo | 42220 | https://celo.rpc.hypersync.xyz or https://42220.rpc.hypersync.xyz | |
| Chainweb Testnet 20 | 5920 | https://chainweb-testnet-20.rpc.hypersync.xyz or https://5920.rpc.hypersync.xyz | |
| Chainweb Testnet 21 | 5921 | https://chainweb-testnet-21.rpc.hypersync.xyz or https://5921.rpc.hypersync.xyz | |
| Chiliz | 88888 | https://chiliz.rpc.hypersync.xyz or https://88888.rpc.hypersync.xyz | |
| Citrea Testnet | 5115 | https://citrea-testnet.rpc.hypersync.xyz or https://5115.rpc.hypersync.xyz | |
| Curtis | 33111 | https://curtis.rpc.hypersync.xyz or https://33111.rpc.hypersync.xyz | |
Expand Down Expand Up @@ -72,11 +74,10 @@ Here is a table of the currently supported networks on HyperRPC and their respec
| Moonbase Alpha | 1287 | https://moonbase-alpha.rpc.hypersync.xyz or https://1287.rpc.hypersync.xyz | |
| Moonbeam | 1284 | https://moonbeam.rpc.hypersync.xyz or https://1284.rpc.hypersync.xyz | |
| Morph | 2818 | https://morph.rpc.hypersync.xyz or https://2818.rpc.hypersync.xyz | |
| Morph Holesky | 2810 | https://morph-holesky.rpc.hypersync.xyz or https://2810.rpc.hypersync.xyz | |
| Opbnb | 204 | https://opbnb.rpc.hypersync.xyz or https://204.rpc.hypersync.xyz | |
| Optimism | 10 | https://optimism.rpc.hypersync.xyz or https://10.rpc.hypersync.xyz | |
| Optimism Sepolia | 11155420 | https://optimism-sepolia.rpc.hypersync.xyz or https://11155420.rpc.hypersync.xyz | |
| Pharos Devnet | 50002 | https://pharos-devnet.rpc.hypersync.xyz or https://50002.rpc.hypersync.xyz | |
| Plume | 98866 | https://plume.rpc.hypersync.xyz or https://98866.rpc.hypersync.xyz | |
| Polygon | 137 | https://polygon.rpc.hypersync.xyz or https://137.rpc.hypersync.xyz | |
| Polygon Amoy | 80002 | https://polygon-amoy.rpc.hypersync.xyz or https://80002.rpc.hypersync.xyz | |
| Polygon zkEVM | 1101 | https://polygon-zkevm.rpc.hypersync.xyz or https://1101.rpc.hypersync.xyz | |
Expand All @@ -91,6 +92,8 @@ Here is a table of the currently supported networks on HyperRPC and their respec
| Sophon Testnet | 531050104 | https://sophon-testnet.rpc.hypersync.xyz or https://531050104.rpc.hypersync.xyz | |
| Superseed | 5330 | https://superseed.rpc.hypersync.xyz or https://5330.rpc.hypersync.xyz | |
| Swell | 1923 | https://swell.rpc.hypersync.xyz or https://1923.rpc.hypersync.xyz | |
| Tangle | 5845 | https://tangle.rpc.hypersync.xyz or https://5845.rpc.hypersync.xyz | |
| Taraxa | 841 | https://taraxa.rpc.hypersync.xyz or https://841.rpc.hypersync.xyz | |
| Unichain | 130 | https://unichain.rpc.hypersync.xyz or https://130.rpc.hypersync.xyz | |
| Unichain Sepolia | 1301 | https://unichain-sepolia.rpc.hypersync.xyz or https://1301.rpc.hypersync.xyz | |
| Worldchain | 480 | https://worldchain.rpc.hypersync.xyz or https://480.rpc.hypersync.xyz | |
Expand Down
Loading