> For the complete documentation index, see [llms.txt](https://docs.zeraxai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeraxai.com/staking/unstaking.md).

# Unstaking

Unstaking allows users to remove their staked ZXAI according to the active staking rules.

The ability to unstake may depend on the selected lock duration.

{% hint style="warning" %}
Some staking options may require the lock period to end before unstaking is available.
{% endhint %}

***

### How Unstaking Works

1. Open the staking section.
2. View your active staking positions.
3. Check the lock status.
4. If available, click unstake.
5. Confirm the transaction in your wallet.
6. Wait for blockchain confirmation.

***

### Lock Status

| Status        | Meaning                                               |
| ------------- | ----------------------------------------------------- |
| **Locked**    | The stake is still inside the lock period.            |
| **Unlocked**  | The lock period ended and unstaking may be available. |
| **Claimable** | Rewards may be available to claim.                    |
| **Completed** | Stake or reward action was completed.                 |

***

### Early Withdrawal

Early withdrawal rules depend on the staking contract and active settings.

If early unstaking is not supported, users must wait until the lock period ends.

{% hint style="danger" %}
Do not stake unless you understand the lock duration and unstaking rules.
{% endhint %}

***

### Summary

Unstaking is used to remove ZXAI from staking after the lock rules allow it.

Always review lock duration, rewards and gas fees before confirming any staking action.


---

# 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.zeraxai.com/staking/unstaking.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.
