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

# Network and links

### div.fun

* **App** — [div.fun](https://div.fun)
* **Docs** — [docs.div.fun](https://docs.div.fun)
* **X / Twitter** — [@divdotfun](https://x.com/divdotfun)

### Network

div.fun runs on HyperEVM, the EVM layer of Hyperliquid.

| Field    | Value                                    |
| -------- | ---------------------------------------- |
| Network  | HyperEVM (Hyperliquid)                   |
| Chain ID | `999`                                    |
| RPC URL  | `https://rpc.hyperliquid.xyz/evm`        |
| Currency | HYPE                                     |
| Explorer | [HyperEVM scan](https://hyperevmscan.io) |

See [connect your wallet](/getting-started/connect-your-wallet.md) to add the network.

### Contract addresses

div.fun's contract addresses are published in the app and verifiable on the [explorer](https://hyperevmscan.io). Each launched token deploys its own set of associated contracts. Always confirm an address against an official div.fun source before interacting with it — never trust an address from an unofficial link.

### Ecosystem

* **Hyperliquid docs** — [hyperliquid.gitbook.io](https://hyperliquid.gitbook.io/hyperliquid-docs)
* **HyperSwap** — [hyperswap.exchange](https://hyperswap.exchange)

### A note on this documentation

These docs explain how div.fun works as a product and a protocol. They describe mechanisms rather than fixed numbers, because a token's terms — its reward asset, dividend share, and split — are set per token and read on-chain, and protocol parameters can evolve. For the live figures of any specific token, read its [page](/for-traders/the-token-page.md) in the app, where every value is read directly from the chain.

### div.fun

* **App** — [div.fun](https://div.fun)
* **Docs** — [docs.div.fun](https://docs.div.fun)
* **X / Twitter** — [@divdotfun](https://x.com/divdotfun)

### Network

div.fun runs on HyperEVM, the EVM layer of Hyperliquid.

| Field    | Value                                    |
| -------- | ---------------------------------------- |
| Network  | HyperEVM (Hyperliquid)                   |
| Chain ID | `999`                                    |
| RPC URL  | `https://rpc.hyperliquid.xyz/evm`        |
| Currency | HYPE                                     |
| Explorer | [HyperEVM scan](https://hyperevmscan.io) |

See [connect your wallet](/getting-started/connect-your-wallet.md) to add the network.

### Contract addresses

div.fun's contract addresses are published in the app and verifiable on the [explorer](https://hyperevmscan.io). Each launched token deploys its own set of associated contracts. Always confirm an address against an official div.fun source before interacting with it — never trust an address from an unofficial link.

### Ecosystem

* **Hyperliquid docs** — [hyperliquid.gitbook.io](https://hyperliquid.gitbook.io/hyperliquid-docs)
* **HyperSwap** — [hyperswap.exchange](https://hyperswap.exchange)

### A note on this documentation

These docs explain how div.fun works as a product and a protocol. They describe mechanisms rather than fixed numbers, because a token's terms — its reward asset, dividend share, and split — are set per token and read on-chain, and protocol parameters can evolve. For the live figures of any specific token, read its [page](/for-traders/the-token-page.md) in the app, where every value is read directly from the chain.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.div.fun/resources/network-and-links.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.