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

# Why Hyperevm

HyperEVM is the general-purpose EVM chain from Hyperliquid. It pairs a familiar Ethereum tooling surface with the speed and finality of the Hyperliquid stack. Hyperlynx is built natively on it.

## What it means for traders

* **Fast finality.** Trades and liquidity moves settle quickly, so the fill lands before the market reacts.
* **Low fees.** Gas is paid in **HYPE**, the native token, and stays cheap relative to mainnet.
* **One chain, no bridge-in-the-middle.** Hyperlynx targets a single network. There's no second chain hidden in the app and no runtime chain-switching.
* **Real EVM.** Standard wallets (Rabby, MetaMask, and other EVM wallets) work out of the box.

## The Hyperlynx thesis

Most venues are noise. Hyperlynx is built to be the calm point of attention on top of HyperEVM:

* **Spot first.** Deep, honest spot liquidity with concentrated-liquidity routing.
* **Stocks day one.** Tokenized equities live at launch, not a roadmap promise.
* **A fee machine, not a farm.** Trading fees flow back to the people who hold and stake. See [The fee machine](broken://pages/f8b39519fd4ccadb994dda29cf193c2d2e6e1e49).

{% hint style="info" %}
You need a small amount of **HYPE** for gas before you can trade. See [Fund your wallet](broken://pages/2e07de052c547263a3dd7ca15dd74ff895bda143).
{% endhint %}


---

# 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://hyperlynx.gitbook.io/hyperlynx-docs/why-hyperevm.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.