> For the complete documentation index, see [llms.txt](https://docs.osero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.osero.com/osero-app/yield+-vaults/how-to-deposit-and-withdraw.md).

# How To Deposit & Withdraw

## Depositing into Yield+

Depositing into Yield+ follows the same flow as Savings.

Connect your wallet, choose USDC or USDT, enter the amount, review the expected goUSDC or goUSDT output, and approve the transaction.

Osero handles any conversions or bridging needed before the funds enter the strategy.

## Withdrawing from Yield+

Yield+ withdrawals are processed by Gauntlet rather than executed instantly. This is because withdrawing requires the strategy to unwind part of its position, including repaying debt and withdrawing collateral from the underlying Morpho markets.

Processing time depends on the size of the withdrawal:

* **Under $50k** - typically processed within 2 hours.
* **Larger withdrawals** - may take longer, as Gauntlet unwinds the position while considering execution costs and the impact on other depositors.
* **Expected maximum** - Osero aims to process withdrawals within 6–12 hours.

Funds are not locked, but withdrawals are processed asynchronously, allowing the strategy to unwind positions efficiently without unnecessarily impacting the vault’s Net APY.


---

# 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.osero.com/osero-app/yield+-vaults/how-to-deposit-and-withdraw.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.