> For the complete documentation index, see [llms.txt](https://haedal-protocol.gitbook.io/haedal-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://haedal-protocol.gitbook.io/haedal-protocol-docs/haedal-liquid-staking/hasui/unstake.md). # Unstake ### Regular Unstake Users can unstake their haSUI to get back SUI freely. The regular unstake operation incurs no fee, but requires a waiting period of 1-2 epochs to cancel the stake. When a user submits an unstake request, Haedal will burn the submitted haSUI and issue a claim object to the user. When the waiting period finishes, the user (with the specific claim object in account) will be able to claim their SUI tokens back. The amount of SUI tokens that can be withdrawn via unstaking is calculated as: $$ SUIamount=haSUIBurntAmount\*haSUIConversionRate $$ There are three scenarios for "Withdraw by Unstake": * If the unstake request is made at the start of epoch n, the user will receive their staked assets in epoch n+1. However, the haSUI exchange rate for epoch n will not be updated, and the user will receive their assets based on the haSUI exchange rate of epoch n-1. * If the unstake request is made during epoch n, the user will receive their assets in epoch n+1. * If the unstake request is made in the last 4 hours of epoch n, the user will receive their assets in epoch n+2. ### Instant Unstake Besides the regular unstake, Haedal also supports SIP33 on Sui to allow for instant unstake. The SIP33 allows inactive StakedSui objects to be redeemed immediately. This creates the premise for instant unstake. Users can opt for instant unstake with a small unstaking fee when they need their SUI urgently. The instant unstaking fee is currently set as 0.02% of the unstaking amount of each request. --- # 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://haedal-protocol.gitbook.io/haedal-protocol-docs/haedal-liquid-staking/hasui/unstake.md?ask=&goal= ``` `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.