> For the complete documentation index, see [llms.txt](https://help.defisaver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.defisaver.com/protocols/sky/dashboard-and-use-case.md).

# Dashboard & Use-case

{% hint style="info" %}
*Users don't need to mint DAI from MakerDAO in order to acquire USDS from Sky. It's also possible to get USDS from a different lending protocol on DeFi Saver.*
{% endhint %}

Besides Sky's obvious use-case of converting DAI with a 1:1 value for USDS, or MKR for SKY (and vice-versa) - The protocol also provides users with opportunity to earn yield on their USDS, or earn SKY tokens.&#x20;

<details>

<summary>Show me how:</summary>

The first step would be visiting the Sky dashboard by clicking on it from the sidebar:

<figure><img src="/files/HJ9v73XgWTvFnoKtGtJa" alt=""><figcaption></figcaption></figure>

Once there, click on the "Savings" tab:

<figure><img src="/files/HkMiBYYLrzffK84YHfh3" alt=""><figcaption></figcaption></figure>

You can then enter the amount of USDS you'd like to stake in order to get sUSDS in return.

Another staking option with USDS is to earn SKY or Chronicle points. Simply visit the "Rewards" tab and choose one of the two options that suit you:

<figure><img src="/files/AFpixyH8qDtU0XsRcZFF" alt=""><figcaption></figcaption></figure>

For example, getting SKY with USDS:

<figure><img src="/files/Nj35yipeoRrdj0WXy9NO" alt=""><figcaption></figcaption></figure>

Once you've deposited into the SSR, you'll find your position on the "Portoflio" page has also been updated to reflect the deposited funds:

<figure><img src="/files/qrIdM6EfucV2GGqkZcBM" alt=""><figcaption></figcaption></figure>

</details>

Users that have already supplied DAI to DSR and hold sDAI can upgrade their savings to SSR directly on DeFi Saver.

<details>

<summary>Show me how:</summary>

From the Sky dashboard, visit the "Upgrade Savings" tab:

<figure><img src="/files/NPRaIUFSGTca4JAKymDb" alt=""><figcaption></figcaption></figure>

From there, you'll be able to upgrade your sDAI received from the DSR to sUSDS - essentially transferring your funds from the DSR to SSR.

</details>

Additionally, there's the option of SKY staking on DeFi Saver:

<details>

<summary>Show me how:</summary>

On the Sky dashboard, click on the "Stake" tab:

<figure><img src="/files/uVBk81rU2qreOMZe3MxW" alt=""><figcaption></figcaption></figure>

Next up, choose between staking SKY for SPK or USDS:

<figure><img src="/files/Qe4A8oSpFwUwkGTyxoU7" alt=""><figcaption></figcaption></figure>

On the next screen, you'll be able to input the amount you'd like to stake, and the panel on the right will show your accrued rewards and APY.

</details>

Seeing as Sky is not a lending protocol, there aren't any automations or other advanced features available within the dashboard, although you can expect all the important metrics (e.g. Estimated earnings) to be present within the dashboard.


---

# 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://help.defisaver.com/protocols/sky/dashboard-and-use-case.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.
