> For the complete documentation index, see [llms.txt](https://takes.gitbook.io/takes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://takes.gitbook.io/takes-docs/reference/supported-networks.md).

# Networks

Your pool’s network is where you buy, hold, sell, and claim shares or proceeds. Every token's trading account is on Hyperliquid, regardless of the network you use.

| Token network | Gas token | Route to the trading account                                                               |
| ------------- | --------- | ------------------------------------------------------------------------------------------ |
| Arc           | USDC      | Separate HyperEVM hub; Standard CCTP deposits and returns.                                 |
| HyperEVM      | HYPE      | Dedicated local hub; no CCTP transfer.                                                     |
| Ethereum      | ETH       | Separate HyperEVM hub; Fast deposits when available, otherwise Standard; Standard returns. |
| Base          | ETH       | Separate HyperEVM hub; Fast deposits when available, otherwise Standard; Standard returns. |
| Arbitrum      | ETH       | Separate HyperEVM hub; Fast deposits when available, otherwise Standard; Standard returns. |
| Monad         | MON       | Separate HyperEVM hub; Standard CCTP deposits and returns.                                 |

Commands normally use Standard finality. Supported Ethereum, Base and Arbitrum testnet deployments can enable Fast commands through an immutable switch; mainnet cannot enable it. Deposits, commands and returns are separate steps. See [Cross-chain security](/takes-docs/security-and-trust/cross-chain-security.md#cross-chain-security) for reorganization risks.

Takes handles the transfers between the token and its trading account. You do not need to bridge each buy or sell request yourself. Completion time depends on network finality and delivery.

## Using the right network

Use the network shown on the token page. Keep USDC there for buying shares and the network's gas token for transactions. On Arc, both use USDC. On other networks, USDC and gas are separate balances.

Arc token creation includes the seed as native USDC. Creation on HyperEVM, Ethereum, Base, Arbitrum, and Monad uses a USDC token allowance. Buy requests require USDC approval when your allowance is insufficient, including on Arc.

Each token stays on the network where it was created. Takes does not move your token between networks or let you buy pool shares using a wallet balance on another network.

To fund a different network before buying shares, see [Trade and move USDC](/takes-docs/trade.md).

See [Fees and limits](/takes-docs/reference/fees-and-limits.md#fees-and-limits) for bridge costs. Monad's gas currency is documented in its [gas guide](https://docs.monad.xyz/developer-essentials/gas-pricing).

See [Contract addresses](/takes-docs/reference/contract-addresses.md#contract-addresses) and [Architecture](/takes-docs/technical-design/architecture-overview.md#architecture).


---

# 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://takes.gitbook.io/takes-docs/reference/supported-networks.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.