> For the complete documentation index, see [llms.txt](https://docs.ethena.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethena.fi/backing-assets/liquid-stablecoins.md).

# Liquid Stablecoins

The protocol holds a portion of its backing in liquid, fiat-referenced stablecoins - such as USDC, USDT, and USDtb - that already maintain a stable dollar value using fiat (and equivalent) reserves and therefore do not require a derivatives hedge.

Liquid stablecoins serve several functions in the backing portfolio. They support the protocol's ability to manage on-demand redemptions, allowing whitelisted counterparties to redeem USDe without the protocol needing to unwind hedged positions in order to source liquidity. 

Liquid stablecoins also act as a safeguard during periods when perpetual funding rates and futures basis are suboptimal, allowing the protocol to reduce hedged exposure while preserving stable backing.

The allocation to liquid stablecoins is dynamic. It is increased or decreased in response to redemption patterns, market conditions, and the relative attractiveness of other backing strategies. Depending on where they are held, certain liquid stablecoins may earn rewards - for example, rewards available on USDC - which can contribute to overall protocol revenue.

<br>


---

# 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.ethena.fi/backing-assets/liquid-stablecoins.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.