> For the complete documentation index, see [llms.txt](https://docs.zirodelta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zirodelta.com/tokens/wzdusd.md).

# wzdUSD

wzdUSD is a share of the [Yield Engine](/modules/yield-engine.md)'s pool, on Solana.

{% hint style="warning" %}
**Not live for customers.** Deposits and redemptions are not open.
{% endhint %}

## What it is

* Each wzdUSD is one share of the pool's main tranche.
* Its value is the pool's share price: the pool's net asset value divided by the number of shares. Holding wzdUSD means holding a balance of shares times that price.
* As the pool earns, the share price rises. If the pool loses more than its first-loss buffer, the share price falls.

## What it is not

wzdUSD is **not a stablecoin**. It does not promise to be worth exactly US$1, and it can be worth less. If you want a token designed to stay at US$1, hold USDC.

## How it is backed

* wzdUSD is minted when shares in the pool are locked behind it, and burned when they are redeemed.
* The [transparency page](https://zirodelta.com/transparency) is designed to show, as each part goes live, that wzdUSD supply never exceeds the shares behind it.

## Using wzdUSD

* **Redeem** it for its share of the pool, once redemptions open.
* **Borrow against it** through the [Credit Engine](/modules/credit-engine.md), once that opens.

## Status

In development.


---

# 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://docs.zirodelta.com/tokens/wzdusd.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.