> 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/vusd.md).

# VUSD

VUSD is the protocol's primary dollar-referenced settlement asset.

VUSD is a protocol-generated dollar-referenced settlement asset, targeting a 1:1 value relationship with the US dollar. It is over-collateralized by a diversified basket of USDC, USDT, frxUSD, and additional stablecoins approved by the protocol team and governance.

## Key Properties

* **Settlement-grade**: designed for high-velocity cross-chain settlement and institutional use
* **Over-collateralized**: backed by a diversified basket of approved stablecoins
* **Omnichain**: natively present on 100+ chains via LayerZero OFT — no wrapping required
* **Redeemable**: on a best-efforts basis subject to liquidity and strategy performance
* **Yield-separated**: VUSD holders do not take on yield strategy risk by default

## Minting VUSD

Users deposit approved stablecoins (USDC, USDT, frxUSD) through the Gateway contract and receive VUSD at a 1:1 rate minus a nominal minting fee. There is no lockup on the base asset.

## Holding VUSD

VUSD held without staking continues to function as a settlement-grade dollar token. The yield generated on its backing collateral flows to the protocol treasury to fund reserves, operations, and governance revenue distribution — this is called **Lazy Yield**.

## Redeeming VUSD

Standard users follow a multi-step redemption flow:

1. Initiate a redemption request specifying the desired stablecoin
2. Wait for the governance-configurable security delay (\~10 blocks / 120 seconds)
3. Finalize with a second confirmation

Whitelisted market makers bypass the security delay and execute instant single-transaction redemptions, limited to the current Treasury buffer balance.

## Reserve Protections

VUSD holders benefit from four layers of protection:

1. A diversified strategy universe targeting 30 independent yield sources at maturity
2. A liquid redemption buffer held outside yield deployment
3. Priority-first redemption treatment relative to sVUSD and VUSDx holders
4. Protocol-maintained self-insurance buffers

## Contract

| Network          | Address                                                                                                               |
| ---------------- | --------------------------------------------------------------------------------------------------------------------- |
| Ethereum Mainnet | [0xCa83DDE9c22254f58e771bE5E157773212AcBAc3](https://etherscan.io/address/0xCa83DDE9c22254f58e771bE5E157773212AcBAc3) |

## Want to Integrate with VUSD?

If you represent a project and want to discuss integrating VUSD or adding a new minting input asset: [Speak to the team →](https://vetro.org/speak-to-the-team)


---

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