> For the complete documentation index, see [llms.txt](https://docs.hemi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hemi.xyz/discover/network-details.md).

# Network Details

Everything you need to connect to the Hemi network.

## Hemi Mainnet

<table><thead><tr><th width="293"></th><th></th></tr></thead><tbody><tr><td>Chain ID</td><td><code>43111</code></td></tr><tr><td>Currency symbol / Gas Token</td><td><code>ETH</code></td></tr><tr><td>RPC URL</td><td><a href="https://rpc.hemi.network/rpc">https://rpc.hemi.network/rpc</a></td></tr><tr><td>Block Explorer URL</td><td><a href="https://explorer.hemi.xyz">https://explorer.hemi.xyz</a></td></tr></tbody></table>

{% hint style="info" %}
Need to bring assets to Hemi? Visit the [**Hemi Tunnel**](https://app.hemi.xyz/en/tunnel/).
{% endhint %}

## Hemi Testnet

{% hint style="warning" %}
Testnet is a testing environment for validating new features and deployments before they reach mainnet. Testnet tokens have no monetary value — do not send real assets to testnet addresses. Hemi testnet may undergo maintenance or be reset without notice.
{% endhint %}

<table><thead><tr><th width="289"></th><th></th></tr></thead><tbody><tr><td>Chain ID</td><td><code>743111</code></td></tr><tr><td>Currency symbol / Gas Token</td><td><code>ETH</code></td></tr><tr><td>RPC URL</td><td><a href="https://testnet.rpc.hemi.network/rpc">https://testnet.rpc.hemi.network/rpc</a></td></tr><tr><td>Block Explorer URL</td><td><a href="https://testnet.explorer.hemi.xyz">https://testnet.explorer.hemi.xyz</a></td></tr></tbody></table>

{% hint style="info" %}
Public RPC endpoints are rate-limited to approximately 300 requests per minute and are intended for development and testing. These limits are subject to change. For production applications, use a third-party provider.
{% endhint %}

***

## Third-Party RPC Providers

We partner with leading node providers to allow dApps to seamlessly integrate with the Hemi network. These providers offer reliable and scalable RPC endpoints, allowing you to concentrate on development while they handle node infrastructure.

#### dRPC

[dRPC](https://drpc.org) provides high-performance RPC access to Hemi, backed by a distributed network of node providers. A free tier is available.

[Sign up at drpc.org →](https://drpc.org)

<table><thead><tr><th width="132.30859375">Network</th><th>HTTPS</th><th>WebSocket</th></tr></thead><tbody><tr><td>Mainnet</td><td><code>https://hemi.drpc.org</code></td><td><code>wss://hemi.drpc.org</code></td></tr><tr><td>Testnet</td><td><code>https://hemi-testnet.drpc.org</code></td><td><code>wss://hemi-testnet.drpc.org</code></td></tr></tbody></table>

#### DIN (via Infura)

[DIN](https://www.infura.io/solutions/decentralized-infrastructure-service) is Infura's Decentralized Infrastructure Network. Hemi is available on all Infura plans, including the free tier. An API key is required.

[Sign up at infura.io →](https://www.infura.io)

<table><thead><tr><th width="131.5390625">Network</th><th>HTTPS</th></tr></thead><tbody><tr><td>Mainnet</td><td><code>https://hemi-mainnet.infura.io/v3/YOUR_API_KEY</code></td></tr><tr><td>Testnet</td><td><code>https://hemi-testnet.infura.io/v3/YOUR_API_KEY</code></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hemi.xyz/discover/network-details.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.