> 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/security-and-audits.md).

# Security & Audits

Osero App does not use its own smart contracts to hold your final savings position.

Your position is held as sUSDS on Sky Protocol infrastructure. Osero prepares the route into sUSDS rather than replacing Sky’s underlying contracts with its own.

Before you receive sUSDS, your transaction may also involve Osero, your wallet, Enso, LI.FI, blockchain networks, and cross-chain infrastructure. Each component has its own risks, so using Osero involves more than just Sky Protocol infrastructure.

### Osero's trust boundary

Osero displays a route for the user to review. Wallets, route providers, networks, and Sky infrastructure remain separate systems, each with its own failure modes. Osero does not control them or remove their risks.

Sky audits cover specific Sky components. They do not cover Osero, every route used by the app, or your wallet and device. Always review the route and wallet requests before signing.

### Sky security in context

Sky Protocol, formerly MakerDAO, has operated for more than 11 years without a reported exploit affecting its core protocol or oracle system.

Its official security index includes more than 50 public security reports covering the core system, governance, savings, tokens, liquidity, bridges, and capital-allocation modules.

These reviews include work from firms such as ChainSecurity, Cantina, Trail of Bits, PeckShield, and Certora. Sky also describes its [development and formal verification practices](https://developers.skyeco.com/security/security-measures/development-practices/) and runs a [bug bounty program](https://developers.skyeco.com/security/bug-bounty-program/) through Immunefi.

This track record provides context on the security work behind Sky infrastructure, but it does not eliminate risk or guarantee that every contract, route, or transaction will work as expected.

### Sky Protocol audits

The reviews below cover Sky Protocol, not Osero App.

Sky’s official audit index lists completed security reviews and the specific protocol components covered by each one.

| Sky component | Listed review firms       |
| ------------- | ------------------------- |
| USDS          | ChainSecurity and Cantina |
| sUSDS         | ChainSecurity and Cantina |
| LitePSM       | ChainSecurity and Cantina |

LitePSM is part of Sky’s infrastructure for converting between USDS and supported stablecoins. Its security reviews are part of Sky’s audit record, rather than audits of the Osero App.

### What reviews cannot prove

Audits, formal checks, and bug bounty reports can reduce uncertainty, but they cannot prove that software is free from bugs or that every route will work as expected. They also do not guarantee that users will not lose funds. \
\
Review the current app details and [Sky's User Risk Documentation](https://docs.sky.money/legal/skybase-international/user-risks) before signing.


---

# 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/security-and-audits.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.