> 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/zdlt-token/wzdusd.md).

# wzdUSD

**wzdUSD is the working dollar of the Zirodelta system, and the dollar you are paid in for holding ZDLT.** It is a yield-bearing dollar that grows over time: the earning line of a programmable personal balance sheet. Rewards accrue to ZDLT holders in wzdUSD, never in ZDLT.

## What it is, and what it is not

wzdUSD is closer to a **liquid-staking token than to a stablecoin**. It is meant to slowly appreciate, not to sit flat at exactly $1.

* It is **not a $1 stablecoin**, and we never call it one.
* It is **backed**, but it is **market-priced**: it can trade a little above or below its backing, especially in a heavy sell-off, the way a liquid-staking token can trade under its true value.
* We tell you exactly what you hold. No peg promise, no "always redeemable at $1" claim.

If you want a fixed $1 token, hold USDC. wzdUSD is the thing that is designed to grow.

## How it is backed

Every wzdUSD is minted only against **locked collateral backed by real USDC**. The system is built so that wzdUSD cannot be minted out of thin air: the supply is checked against the collateral that backs it.

That backing logic is built and tested, but the vault that holds it is **unaudited and closed to user money** until an independent security audit and a legal review are complete. Until then, wzdUSD exists in a proving phase, not as an open product. See [Vault Overview](/vault/overview.md).

## Why holders are paid in a dollar, not in ZDLT

Paying rewards in wzdUSD instead of ZDLT does two things at once:

1. **No dilution.** Paying holders never requires minting or selling ZDLT, so the token you hold is never watered down to pay you.
2. **Real value, not inflation.** You are paid in a dollar that holds and grows value, not in more of a token whose price you are hoping goes up.

## Paid more the longer and the more you hold

Your share of the wzdUSD reward pool is set by how much ZDLT you hold and how long you have held it. [Tiers](/zidee-wallet/tiers.md) raise your multiplier as your balance grows, and staying (rather than selling and re-buying) compounds your position. This is the mechanism behind "a token that pays you to stay."

## Where the wzdUSD yield comes from

The reward pool is funded by a real, delta-neutral funding-capture strategy on Hyperliquid, the [Yield Engine](/the-zirodelta-financial-engine/overview.md), part of the Zirodelta Financial Engine, not by new deposits and not by printing tokens. That yield is **variable**: it can be low or even zero, and it is never guaranteed. The strategy is currently being proven on the founder's own capital first, on a public address, before user funds are accepted.

## The honest version

* wzdUSD is not a stablecoin and can trade below its backing short-term.
* The yield behind it is variable and can be zero.
* The backing vault is unaudited and not yet open to user money.
* Nothing here is financial advice.


---

# 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.zirodelta.com/zdlt-token/wzdusd.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.