> For the complete documentation index, see [llms.txt](https://vaultbook.gauntlet.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vaultbook.gauntlet.xyz/vaults/gauntlet-usd-alpha-vault/how-to-supply.md).

# How to Supply

<a href="https://app.gauntlet.xyz/vaults/gtusda?utm_source=website&#x26;utm_medium=vaultbook&#x26;utm_campaign=page1" class="button primary" data-icon="circle-right">Explore the Vault</a>

### **Supply**

Capital allocators supply USDC into the vault via the [Gauntlet App](https://app.gauntlet.xyz/vaults/gtusda) on Base, Arbitrum, Optimism, and Ethereum Mainnet.

{% embed url="<https://www.youtube.com/watch?v=39Ia7UQgiMc>" %}

### **Receive gtUSDa**

Suppliers receive gtUSDa, an ERC-20 token that is a claim on the supply amount plus earnings. Supply is reflected onchain within 6-12 hours.

### **Yield Optimization**

Our automated optimization engine, combined with our risk management platform, selects various cross-chain opportunities for the vault to execute. This includes Morpho vaults on Base, Ethereum Mainnet, Arbitrum, and Optimism. The strategy optimizes for available yields within the opportunity set, considers TVL levels, assesses impacts from the size of a given allocation, and generates sustainable real yield.

### **Incentives**

Morpho Rewards/incentives are regularly converted to USDC and redeployed to the strategy. Gauntlet USDC Rewards are regularly streamed by Sablier.

### **Withdrawal**

USDC withdrawal requests can be initiated at any time for gtUSDa. Transactions complete within 6-12 hours on average.


---

# 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://vaultbook.gauntlet.xyz/vaults/gauntlet-usd-alpha-vault/how-to-supply.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.