> For the complete documentation index, see [llms.txt](https://doc.zoofi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.zoofi.io/berachain-eco/liquidity-vault-l-vault/stablecoin-zusd.md).

# Stablecoin--ZUSD

## What is ZUSD? <a href="#what-is-usb" id="what-is-usb"></a>

Like the DAI in the MakerDAO protocol, ZUSD is a decentralized, asset-backed circulating token designed with a price using Oracle feeds, serving as a soft peg to the US dollar.

## How to Obtain ZUSD? <a href="#how-to-obtain-usb" id="how-to-obtain-usb"></a>

ZUSD is minted through the process of depositing collateral into the L-Vault. The protocol supports a variety of assets for minting ZUSD. Conversely, holding ZUSD grants users the ability to redeem their collateral from the Vault, with each ZUSD token representing $1 worth of collateral. This design effectively ties the value of ZUSD to the US dollar, ensuring its stability and reliability as a medium of exchange.

## Where do the earnings come from? <a href="#where-do-the-earnings-come-from" id="where-do-the-earnings-come-from"></a>

ZUSD is a rebasable, interest-bearing stablecoin, generating earnings through financing interest paid by holders of margin tokens.


---

# 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://doc.zoofi.io/berachain-eco/liquidity-vault-l-vault/stablecoin-zusd.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.