> 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/safety-and-resources/faq.md).

# FAQ

## General

<details>

<summary>What is Osero App?</summary>

Osero App is a consumer product for earning on stablecoins without having to navigate the complexity of DeFi yourself. **Savings** gives you the base Sky Savings Rate through sUSDS, while **Yield+** uses a Gauntlet-curated strategy with leverage to target higher yield with additional risk. See [What Is Osero](/osero-app/osero-app/what-is-osero-app.md) for a short overview of both.

</details>

<details>

<summary>What asset do I receive?</summary>

With **Savings**, you receive sUSDS, the yield-bearing savings token issued by Sky. With **Yield+**, you receive goUSDC or goUSDT, representing your share of the corresponding Gauntlet-curated vault. Before depositing, Osero displays the current route and expected output for your review.

</details>

<details>

<summary>What are USDS and sUSDS?</summary>

USDS is a dollar-pegged stablecoin issued by Sky. sUSDS is its yield-bearing savings token. As the Sky Savings Rate accrues, each sUSDS token can represent more USDS over time. For more details on how the two work, see [USDS](/osero-app/sky-foundations/what-are-susds-and-usds.md) and [sUSDS](/osero-app/sky-foundations/what-are-susds-and-usds.md).

</details>

<details>

<summary>Why do I receive fewer sUSDS than the stablecoin I deposit?</summary>

sUSDS has a higher value per token than USDC or USDS. For example, if 1 sUSDS represents 1.10 USDS, depositing 1,000 USDC would give you roughly 909 sUSDS before fees or price changes.

Receiving fewer tokens does not mean you are losing value. Each sUSDS represents more USDS, and as the Sky Savings Rate accrues, that amount can increase over time.

</details>

## Using Osero App

<details>

<summary>Which assets and networks can I use?</summary>

Osero supports the stablecoins and networks shown in the app. **Savings** supports the full range of available assets and networks, while **Yield+** currently accepts USDC and USDT.

See [**How Osero App Works**](/osero-app/osero-app/how-osero-app-works.md) for Savings and [**Depositing into Yield+**](/osero-app/yield+-vaults/how-to-deposit-and-withdraw.md) for Yield+. Supported options may change over time, so check the app for the latest availability.

</details>

<details>

<summary>How does a deposit work?</summary>

Choose an available input asset and network, enter the amount, and review the route together with the expected sUSDS output. The app then presents the wallet requests needed for the transaction, which you should check before approving. See [How Osero App Works](/osero-app/osero-app/how-osero-app-works.md) for the full deposit path.

</details>

<details>

<summary>Can I withdraw?</summary>

For Savings, you can withdraw when the current app supports a route for your sUSDS position. The app shows the available output, route, fees, and wallet requests before you sign, and these can change based on network conditions and liquidity.

For Yield+, withdrawals are curator-executed: requests under $50k typically complete in under 2 hours, and larger requests are handled with greater care regarding execution costs, with a target of 6–12 hours. See [Withdrawals from Yield+](/osero-app/yield+-vaults/how-to-deposit-and-withdraw.md).

</details>

## Yield+

<details>

<summary>What's the difference between Savings and Yield+?</summary>

**Savings** holds sUSDS directly and earns the base Sky Savings Rate. **Yield+** uses that same sUSDS yield source with leverage through Aera V3 and Morpho Blue to target a higher Net APY. The strategy is curated and risk-managed by Gauntlet and carries additional risk.

</details>

<details>

<summary>What do goUSDC and goUSDT represent?</summary>

They are ERC-4626 receipt tokens representing your share of the corresponding Yield+ vault. Their value grows as the underlying strategy earns yield.

</details>

<details>

<summary>Who controls the leverage?</summary>

Gauntlet’s risk engine continuously manages leverage within the onchain limits set by Aera V3. It can only perform approved actions, such as supplying, borrowing, swapping, and rebalancing, within the defined leverage parameters.

</details>

<details>

<summary>Why do Yield+ withdrawals take longer than Savings withdrawals?</summary>

Yield+ withdrawals require the strategy to unwind part of its position, including repaying debt and withdrawing collateral from Morpho. Smaller withdrawals are typically processed faster, while larger requests may take longer due to execution costs.

</details>

<details>

<summary>Can Yield+ operate without leverage?</summary>

Yes. If borrowing costs make leverage unattractive, Gauntlet can reduce the strategy to 1x, meaning no borrowed exposure is used to amplify the sUSDS yield.

</details>

## USDS, sUSDS & Rate

<details>

<summary>Where does the rate come from?</summary>

The Sky Savings Rate is set through Sky governance. Osero displays the rate used by the savings route, but Osero does not set or control it. See [sUSDS](/osero-app/sky-foundations/what-are-susds-and-usds.md) for an explanation of how the rate relates to the sUSDS share token.

</details>

<details>

<summary>Can the rate change?</summary>

Yes. Sky governance can change the rate, so the value shown in the app should not be treated as fixed or as a promise of future returns. Check the current rate and the other transaction details at the time you use the app.

</details>

<details>

<summary>Does Osero manage the USDS peg?</summary>

No. The Sky ecosystem governs and operates the mechanisms that support the USDS peg. Osero can present a route that uses Sky infrastructure, but it does not control those mechanisms. Read [Peg Mechanism](/osero-app/sky-foundations/peg-mechanism.md) for more context.

</details>

## Security & Risk

<details>

<summary>Does Osero App use new smart contracts?</summary>

Osero App does not add Osero smart contracts that hold the final savings position. The final position is sUSDS on Sky infrastructure. A route may still involve the Osero interface, your wallet, Enso, LI.FI, a network, or a cross-chain path before sUSDS is created, and each of those parts can carry its own risks.

</details>

<details>

<summary>Are the listed audits Osero audits?</summary>

No. The listed ChainSecurity and Cantina reviews belong to Sky components such as USDS, sUSDS, and LitePSM. Aera V3 and Morpho Blue, used by Yield+, have their own separate audit histories. These help explain the infrastructure used by the final position, but they do not audit Osero, every route, or your wallet. See [Security & Audits](/osero-app/safety-and-resources/security-and-audits.md) for the distinction.

</details>

<details>

<summary>Is my principal protected or guaranteed?</summary>

No protection or guarantee is promised. The value and usability of a position can be affected by contract, stablecoin, market, liquidity, route, wallet, and network risks. Read [Risks](/osero-app/safety-and-resources/risks.md) and Sky's [User Risk Documentation](https://docs.sky.money/legal/skybase-international/user-risks) before using the app.

</details>

<details>

<summary>What should I check before signing?</summary>

Check the input asset, network, route, expected output, fees, and every wallet request. Also confirm that the website and wallet are the ones you intended to use, and rely on the live app details for the action you are preparing. A confirmed blockchain transaction may not be reversible.

</details>


---

# 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/safety-and-resources/faq.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.
