> For the complete documentation index, see [llms.txt](https://docs.pharos.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.xyz/native-staking/stake-and-unstake.md).

# Stake and Unstake

Delegators stake native PROS with a validator pool. A validator's owner uses a separate [withdrawal and exit flow](https://docs.pharos.xyz/native-staking/validator-guide/withdraw-or-exit.md).

## Before You Stake

Select the correct network and keep enough PROS in your wallet for transaction fees. Follow [Delegate PROS](https://docs.pharos.xyz/native-staking/delegation.md) for validator selection, delegation limits, and approval requirements.

## Stake PROS

1. Choose an **Active** or **Pending Add** validator that accepts delegation. A validator pending exit cannot accept new delegations, even if it still appears in the active set.
2. Submit the delegation transaction. If the amount exceeds the pool's remaining capacity, the excess is returned; use the confirmed transaction result for the accepted amount.
3. The accepted PROS becomes **pending stake**, effective at the next epoch. No separate activation transaction is required.

Rewards begin only after the pool is active and your stake participates in reward snapshots. While you have stake awaiting activation in a pool, you cannot add another delegation or unstake from that pool. Pending delegation cannot be cancelled.

## Unstake and Withdraw

Unstaking has two steps: **request a withdrawal**, then **claim it after the exit period**.

1. Request all or part of your effective stake. A full withdrawal includes all currently unclaimed rewards; a partial withdrawal includes a proportional share. Any stake left in the pool must meet the minimum delegation amount.
2. Wait until the request's **unlock epoch**. The default window is **84 epochs**, approximately **14 days** at the default epoch duration. Use the request's actual unlock epoch to determine availability.
3. Submit a claim transaction to receive the unlocked PROS in your wallet. Unlocking does not automatically transfer funds.

Withdrawal requests cannot be cancelled. The requested amount is fixed and stops earning rewards; unstaking during an epoch also excludes the withdrawn portion from that epoch's rewards.

The contract supports multiple withdrawal requests, up to **64 outstanding requests per user per pool**. Unlocked but unclaimed requests also count toward this limit. Ordinary delegators can stake again while these requests are pending, subject to the normal delegation conditions, but cannot compound until all withdrawals are claimed. Any outstanding request from the legacy withdrawal system must be claimed before delegating again or requesting another withdrawal in the same pool.

If a validator exits, your funds remain yours to withdraw. The validator owner cannot withdraw your PROS, and the owner's exit does not automatically create your withdrawal 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pharos.xyz/native-staking/stake-and-unstake.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.
