> 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/delegation.md).

# Delegate PROS

Delegation lets you stake PROS with a validator without running a node. Your stake contributes to the validator pool's total stake, and you share in its rewards after commission. Your position is recorded in the staking contract; the validator owner cannot withdraw your PROS.

Each position is tracked by your wallet address and pool ID. Rewards, pending stake, and withdrawals are managed separately for each pool.

## Choose a Validator

Check the pool's status before delegating:

| Status           | Delegation availability                                                                                                            |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Active**       | Accepts delegation when enabled and capacity is available.                                                                         |
| **Pending Add**  | Can accept delegation to reach the activation threshold. Rewards begin only after activation and inclusion in the reward snapshot. |
| **Pending Exit** | Does not accept new delegation, even while still in the active set.                                                                |
| **Inactive**     | Does not accept new delegation. Existing positions can still be withdrawn through the normal process.                              |

Review the validator's commission and delegation settings. A pool may require a signature from its designated approver. Delegation must be enabled even when approval is not required.

The default minimum delegation is **1 PROS**, and the default pool capacity is **50,000,000 PROS**. A smaller amount is accepted if it exactly fills the remaining capacity. Actual limits depend on the network configuration.

## Submit a Delegation

1. Select [Pacific Mainnet](https://docs.pharos.xyz/getting-started/network/pacific-mainnet.md) or [Atlantic Testnet](https://docs.pharos.xyz/getting-started/network/atlantic-testnet.md), and confirm the pool ID and amount.
2. Keep enough PROS available for transaction fees. Delegation sends native PROS with the transaction; no ERC-20 approval is needed.
3. Submit the delegation. Open pools use `delegate(poolId)`. Pools requiring approval use `delegateWithApproval(poolId, signature)` with the designated approver's signature.
4. Wait for confirmation. If your amount exceeds the remaining pool capacity, the excess is returned. The confirmed `StakeDelegated` event records the accepted amount and activation epoch.

New delegations are unavailable while the staking contract is paused. A full pool cannot accept additional stake. See the [Developer Guide](https://docs.pharos.xyz/native-staking/developer-guide.md#delegation-and-rewards) for transaction checks and approval details.

## Activation and Rewards

Accepted PROS first becomes **pending stake** and becomes effective at the next epoch. No separate activation transaction is needed. Rewards start when the stake is included in an active pool's reward snapshot; becoming effective in a pool still in the bootstrapping state does not start rewards.

While your stake is awaiting activation, you cannot add another delegation, unstake, or compound in the same pool. Pending delegation cannot be cancelled.

After activation, you can add more stake, [claim or compound rewards](https://docs.pharos.xyz/native-staking/rewards-and-claiming.md), or [request a withdrawal](https://docs.pharos.xyz/native-staking/stake-and-unstake.md#unstake-and-withdraw), subject to each action's conditions. Claiming rewards leaves your delegation in place; withdrawing stake requires the exit period and a separate claim.


---

# 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/delegation.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.
