> 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-stake-usx-susx.md). # How To Stake (USX → sUSX) {% embed url="" %} ### **Steps** * Go to the "Earn" tab in the navbar → [usx.capital/earn](https://www.usx.capital/earn) * Connect and verify your wallet * Click the "Stake" button and choose how much USX you want to stake * Sign the transaction in your wallet. Once confirmed, you'll receive sUSX in your wallet. * You can view your sUSX on the “Earn” and “Portfolio” pages. ### Notes sUSX is the yield-bearing token users receive when staking USX. **Holding sUSX automatically accrues rewards,** with no additional action required. As the protocol accumulates rewards in the staking contract, the value of sUSX increases over time relative to USX.

Overview of staking and unstaking process

#### Staking Rewards Mechanism * At launch, the exchange rate is **1 sUSX = 1 USX** * As yield accrues, the value of sUSX gradually increases relative to USX * When staking, users receive sUSX based on the **current exchange rate**. * The number of sUSX tokens you receive may be lower than the USX staked. Over time, the net asset value (NAV) of sUSX is designed to increase with strategy performance, though it may fluctuate in the short term. --- # 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-stake-usx-susx.md?ask=&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.