> For the complete documentation index, see [llms.txt](https://docs.firelight.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firelight.finance/for-stakers/unstaking-and-withdrawals.md).

# Unstaking and Withdrawals

Unstaking is a two-step process: initiate, then withdraw.

#### Step 1: Initiate

The staker submits an unstake request specifying the amount to unstake. On submission the protocol records the request and the position enters the unstaking window. The corresponding stXRP is redeemed at the time of request a snapshot of its redemption value is taken. Redemption ends emissions accrual immediately and removes the position from the next period boundary's coverage-capacity calculation.

{% hint style="info" %}
The unstaking window is **one full period after the period in which the unstake is initiated**: the underlying FXRP becomes withdrawable at the end of the period following the unstake.

**Currently (30-day periods):** the unstaking window is 30 to 60 days, depending on when in the period the unstake is initiated. This is because staked collateral is actively backing coverage. The window is set so that capital cannot exit ahead of the coverage obligations it backs.
{% endhint %}

#### Step 2: Withdraw

After the unstaking window ends, the staker returns to withdraw the underlying. Withdrawing executes the final transfer from the vault to the staker's address. Withdrawals are not automatic, a staker who initiates an unstake but never returns to withdraw leaves the assets in the vault until they submit the withdrawal transaction.

#### Unstaking Window

Since the unstaking window ends at a period boundary rather than a fixed number of days after initiation, the total length of the unstaking window depends on when in the period they initiate. With today's 30-day periods, this means an effective lock of 30 to 60 days. The protocol does not add additional waiting on top of the window.

<figure><img src="https://2979172050-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlY185tQLByKxfPBwxS9v%2Fuploads%2FRPe941a6T32RbHHsqOY2%2Funstaking_window.png?alt=media&amp;token=7aaf8acf-53bd-4390-96b8-309bd9807c82" alt=""><figcaption></figcaption></figure>

The diagram shows two unstake scenarios (Day 10 and Day 29 of Cover Period 0) that both become withdrawable at the same moment at the end of Cover Period 1.

**Slash exposure during the unstaking window**

Redeeming the stXRP ends reward accrual, but it does not end slashing exposure. The window has two phases:

**Backing coverage:** Your capital is still backing coverage in Firelight for the remainder of ther period where you initiated the unstaking process. If an exploit incident occurs during this period, the pending withdrawal takes the same pro-rata slash as active positions.

**Reconciliation window:** Your capital no longer backs new coverage and is not exposed to incidents that occur in this period. However, if an exploit incident is attributed to a period in which your capital was still backing coverage, the resulting slash still applies to the pending withdrawal.

#### Rewards during unstaking window

Emissions stop accruing at the moment an unstake is initiated because the stXRP is redeemed at initiation and its redemption value is snapshotted then. A position in the unstaking window earns neither base rate emissions nor a share of protocol emissions.

### Interactions with coverage matching

When an unstake is initiated, the redeemed stXRP is excluded from the next period boundary's capacity calculation. This is handled by the protocol. From the staker's perspective the only concern is the unstaking window length.

### Blocklist and rescues

Vaults implement a blocklist to comply with regulatory requirements. Blocklisted addresses cannot deploy, withdraw, or transfer. Authorized roles can rescue assets from blocklisted accounts and reassign them to a non-blocklisted address, preserving the position without violating compliance constraints. Most stakers never interact with these mechanics.

### Summary of operational parameters

| Parameter                | Value at feature-complete launch                                                          |
| ------------------------ | ----------------------------------------------------------------------------------------- |
| Deployment activation    | Without waiting for a period boundary                                                     |
| Reward streaming cadence | Regular (targeting steady accrual)                                                        |
| Unstaking window         | One full period after the period of initiation. Currently 30–60 days with 30-day periods. |

Values are subject to adjustment after launch.

### Where to read next

* [Emission Mechanics](https://docs.firelight.finance/for-stakers/emission-mechanics.md) covers what accrues during an active position.
* [Risk and Exposure](https://docs.firelight.finance/for-stakers/risk-and-exposure.md) covers slashing and how deployments feed coverage capacity.


---

# 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.firelight.finance/for-stakers/unstaking-and-withdrawals.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.
