> For the complete documentation index, see [llms.txt](https://doc.lockerprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.lockerprotocol.com/browser-extension/hyperliquid-perps/hype-and-hyperevm.md).

# HYPE between HyperCore and HyperEVM

Move HYPE between your Hyperliquid spot balance and the HyperEVM network.

Hyperliquid has two sides. **HyperCore** is the exchange, where your spot balance lives. **HyperEVM** is the blockchain next to it (chain id 999), where HYPE is the network's own coin and pays the gas. Your address is the same on both, and the wallet moves HYPE between them in one tap.

## What you need

* Some **HYPE** on one side or the other.
* Your Vault: both legs are signed there.

{% stepper %}
{% step %}

### Find the HyperCore spot block

Perps tab → the third block of the balance card, **HyperCore spot**. It shows **HYPE on HyperCore** and the two buttons **To HyperEVM** and **From HyperEVM**.

<figure><img src="https://3674012151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2jyfPJ4rcVavAvTU9nL%2Fuploads%2Fgit-blob-f8563dfe3dcf0974464c9738a86d14b56fc5abc0%2F01-agent-setup.png?alt=media" alt="spot section"><figcaption><p>The HyperCore spot block and its two legs.</p></figcaption></figure>
{% endstep %}

{% step %}

### To HyperEVM

**HYPE to HyperEVM**: *Move HYPE from your Hyperliquid spot balance (HyperCore) to the same address on HyperEVM, where it is the network's native coin. No fee, usually credited within seconds. The transfer is signed by your vault.* **Available on HyperCore** is what you can move.

On the Vault the request reads **HYPE to HyperEVM**, with the amount and the destination. If the destination is neither HyperEVM nor your own account, the Vault says so in red: *this sends your spot balance to someone else… refuse unless you chose this address yourself.*

<figure><img src="https://3674012151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2jyfPJ4rcVavAvTU9nL%2Fuploads%2Fgit-blob-8a22a7c8ba6ba678e162c3d25640c394c0367e7e%2F02-to-hyperevm.png?alt=media" alt="to hyperevm"><figcaption><p>The HyperCore → HyperEVM form.</p></figcaption></figure>
{% endstep %}

{% step %}

### From HyperEVM

**HYPE to HyperCore**: *Send HYPE from HyperEVM to your Hyperliquid spot balance (HyperCore), same address. A normal HyperEVM transaction, its fee paid in HYPE, signed by your vault.*

<figure><img src="https://3674012151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2jyfPJ4rcVavAvTU9nL%2Fuploads%2Fgit-blob-cf9190bd2146e9b93684755049d0eb69de5b2a61%2F03-from-hyperevm.png?alt=media" alt="from hyperevm"><figcaption><p>The HyperEVM → HyperCore form.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The two legs appear in **Activity** as **HYPE to HyperEVM** and **HYPE to HyperCore**. Amounts are capped at eight decimals on both sides; the wallet refuses more.
{% endhint %}

## Learn more

* [Supported networks & chains](/reference/supported-networks.md)
* [Deposit & withdraw USDC](/browser-extension/hyperliquid-perps/deposit-and-withdraw.md)


---

# 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://doc.lockerprotocol.com/browser-extension/hyperliquid-perps/hype-and-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.
