> For the complete documentation index, see [llms.txt](https://docs.osero.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.osero.org/osero-app/safety-and-resources/risks.md).

# Risks

Osero App provides a simple way to access stablecoin savings via Sky Protocol. It simplifies the process, but the underlying risks related to assets, smart contracts, markets, liquidity, and networks still apply.

Before using the Osero App, read the [Skybase International User Risks](https://docs.sky.money/legal/skybase-international/user-risks) and ensure you understand every action you approve.

### Why a route can involve several risks

A single transaction can involve the input asset, your wallet, the Osero interface, route providers, networks, swaps, and Sky contracts.

If something goes wrong at any step, the transaction may fail, take longer than expected, or result in a different amount than expected.

### Sky smart contract risk

The final savings position is sUSDS on Sky infrastructure. A bug, exploit, or design issue in a Sky contract could affect USDS, sUSDS, or the way those assets move.

Audits and security reviews can reduce this risk, but they cannot eliminate it completely.

### Stablecoin and market risk

USDS and other stablecoins used in a transaction can trade at a premium or discount to their intended value. Their price and liquidity can be affected by their backing, reserves, governance, and market conditions.

Significant market movements or problems with a stablecoin involved in the transaction could affect the position or transaction result.

### Liquidity and execution risk

The quote shown in the app reflects conditions when the route is prepared. Liquidity, market depth, and network demand can change before the transaction completes, which may affect the final output, route, or fees.

Always check the latest quote before signing.

### Cross-chain and routing risk

Enso and LI.FI can help move assets across supported networks, but each bridge, swap, network, and contract adds another dependency. Delays, failed messages, price changes, or other issues along the route can affect the transaction or cause a loss.

The route shown in Osero reflects the current details of the transaction you’re about to approve.

### Wallet, front-end, and network risk

A fake website, a compromised device, an incorrect network, a wallet error, or a network outage can cause a transaction to fail or result in lost funds. Once a blockchain transaction is confirmed, Osero cannot reverse it or recover funds sent to the wrong address.

### How to use this risk overview

Before signing, check the stablecoin, network, route, expected output, fees, and wallet requests. Rates and amounts shown in Osero reflect the current quote and may change before the transaction is completed.

Product details may also change over time, so check the latest information in the Osero App and the relevant Sky documentation.


---

# 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.osero.org/osero-app/safety-and-resources/risks.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.
