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

# VUSDx

VUSDx provides predictable, fixed-rate yields through an epoch-based design. Users lock VUSD for the epoch duration and receive a guaranteed yield at maturity.

## Epoch Lifecycle

Each epoch follows this structure:

| Phase                  | Day        |
| ---------------------- | ---------- |
| Deposit window open    | Day 0      |
| Locked — yield accrues | Days 1–23  |
| Exit window (7 days)   | Days 23–29 |
| Payout / auto-rollover | Day 30     |

Each epoch has a published fixed rate, a deposit cap (with a "sold out" state), and automatic rollover enabled by default. Exit requires user action during the exit window.

## Yield Sourcing

Fixed yield is sourced through forward yield rate locking mechanisms at epoch initialization — specifically via purchasing Pendle Protocol's Principal Tokens (PT). A safety buffer is maintained between the locked rate and the advertised VUSDx rate to absorb market movements.

Mid-epoch deposits receive a reduced "gap rate" to prevent late-entry arbitrage.

## Protocol Rationale

VUSDx provides the strongest stability primitive in the protocol:

* **Deterministic Deployment Horizon**: Fixed-term locks give the Treasury absolute certainty over reserve asset commitments, enabling access to the longest-duration, highest-yielding institutional strategies
* **Peg Integrity Floor**: Aggregating a significant portion of VUSD into fixed epochs creates an enduring "sticky TVL" floor that absorbs broader market shocks


---

# 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.vetro.org/products/vusdx.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.