# 2.5 - USDH

USDH is Hyperliquids native stablecoin, built to make “stable liquidity” actually **feed the chain**, not an external issuer.

Most stablecoins export value from a chain, reserves earn yield elsewhere, and the ecosystem gets convenience but does not have compounding alignment. USDH flips that. [**A programmatic share of USDH revenue (50%) is contributed to Hyperliquid’s Assistance Fund**](https://nativemarkets.com/), creating a structural HYPE buy demand as USDH adoption grows.

<figure><img src="/files/00ad09be1846e4d4b0c8ea6be223d879629f754c" alt=""><figcaption></figcaption></figure>

nest is the **default liquidity hub** for USDH:

* it becomes the clean quote asset for most markets (TOKEN/USDH)
* it improves routing and execution (deep stable rails reduce fragmentation)
* it enables stable-denominated strategies across the wider stack in the HyperEVM

{% hint style="success" %}
Every ecosystem needs a monetary base. On Hyperliquid, the “best” base asset is the one that **compounds back into HYPE demand**. USDH is designed to do exactly that.
{% endhint %}

***

#### Why supporting USDH is HYPE-aligned

nest is built to make USDH the **routing core** for HyperEVM liquidity, deep stable markets that make every other asset easier to trade, launch, and build around.&#x20;

**nest’s role** is to concentrate real, usable USDH liquidity on HyperEVM (not fragmented, mercenary stable liquidity), so the ecosystem gets:

* deeper markets → better execution → more onchain volume
* more USDH adoption → more aligned value flow
* stronger, more persistent HYPE-aligned demand loops
* Hype Must Grow thesis aligned


---

# Agent Instructions: 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:

```
GET https://docs.usenest.xyz/nest-explained/2.5-usdh.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.