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

# Unbonding

### Initiating an Unbonding

1. **Open the Staking Section**\
   From the **Quicksilver WebApp**, navigate to the **Staking** area and select the network (or zone) from which you wish to unbond.
2. **Connect Your Wallet**\
   Ensure your wallet is connected (e.g., Keplr or another supported wallet) to authorize the unbonding transaction.
3. **Choose the Amount**
   * If you hold **qATOM**, for instance, you may choose the **full** or **partial** amount you wish to unbond.
   * The **“half”** shortcut button automatically populates half of your available qAssets.
   * An **indicative** estimate of the **final returned amount** in native tokens is shown (based on the **current redemption rate**).
4. **Confirm the Transaction**
   * When ready, click **“Unstake”** (or the equivalent UI button) and **sign** the transaction in your connected wallet.
   * The transaction is queued for processing, typically **triggered** at the **next epoch boundary** (every 3 days by default).

#### Important Details

* **Redemption Rate Variations**\
  The **final** amount of native tokens you receive is determined by the **redemption rate** **at the time** the unbonding is actually processed—this could differ slightly from the initial estimate if the redemption rate changes.
* **Queue Mechanics**
  * Normally, unbondings are processed at the **next epoch**.
  * If your unbonding remains queued due to network constraints (e.g., heavy redelegation activity), the system will **retry** it in the **following epoch**.

<figure><img src="/files/E8sdZzGEhbpFlAZOpIi9" alt=""><figcaption><p>Unstaking Interface</p></figcaption></figure>

### Monitoring Active Unbondings

After submitting an unbonding transaction, you can track its **status** in the **Assets** section of the Quicksilver WebApp:

* **QUEUED**: The unbonding request has been recognized but not yet processed.
* **PENDING**: The system is awaiting the next epoch boundary to finalize your redemption time.
* **COMPLETION TIME**: This field will remain **PENDING** until the unbonding is processed and a final completion time is confirmed.

Once the unbonding is completed, you will receive the corresponding **native tokens** in your wallet on the **origin chain**.

<figure><img src="/files/MeHWmknFb4SB7ADwFaku" alt=""><figcaption><p>Active Unbondings on the Assets page</p></figcaption></figure>

### Key Takeaways

1. **Unbonding Flow**: Submit a request → Wait for the next epoch → Tokens are converted according to the current redemption rate.
2. **Redemption Rate Dynamics**: The actual number of native tokens received depends on the redemption rate at processing time, not at the initial request.
3. **Queued Transactions**: In rare cases of heavy network usage, unbondings may remain in the queue through multiple epochs, but typically process promptly at the **very next** epoch boundary.

This unbonding mechanism respects the **native chain’s rules** while providing a clear, straightforward path to reclaim your staked assets via **Quicksilver’s** liquid staking protocol.