> For the complete documentation index, see [llms.txt](https://docs.usx.capital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usx.capital/guides/using-susx/how-to-unstake-susx-usx.md).

# How To Unstake (sUSX → USX)

### Important

Unstaking is instant. There is no cooldown or waiting period. When you unstake sUSX, you receive USX immediately in your wallet.

{% embed url="<https://player.vimeo.com/video/1181124593>" %}

### Steps

* Navigate to the "Earn" or "Portfolio" page in the navbar - [usx.capital/earn](https://www.usx.capital/earn)
* Connect your wallet and click the "Stake" button.
* Select the **Unstake** tab and enter the amount of sUSX you want to unstake. You'll see how much USX you'll receive.
* Click on **"Unstake"** button.
* Sign the transaction. USX arrives in your wallet immediately.

### Notes

When users unstake their sUSX, they receive USX equal to their initial stake plus any protocol revenue earned through staking.

**Important:** Yield is distributed linearly over a 7-day cycle and if you unstake mid-cycle, you receive yield accrued up to that point.

> **Note**: Holding USX does not generate yield. To earn yield, you need to [stake your USX](/guides/using-susx/how-to-stake-usx-susx.md).


---

# 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.usx.capital/guides/using-susx/how-to-unstake-susx-usx.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.
