> 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/rewards-and-claiming.md).

# Rewards and Claiming

## How Rewards Work

Staking rewards are processed at epoch boundaries using effective stake snapshots. When staking rewards are enabled, a validator pool receives inflation rewards and its allocated transaction priority fees. The validator's commission is deducted first; the remaining rewards are shared in proportion to effective stake.

Base transaction fees are burned. See the [Gas Model](https://docs.pharos.xyz/getting-started/gas-model.md) for fee details.

New delegations and compounded rewards become effective at the next epoch. They earn rewards only when included in an active pool's reward snapshot. Rewards for an epoch still in progress are not yet available to claim.

## Claim Rewards

`claimReward(poolId)` sends all available, unclaimed rewards from that pool to your wallet. It does not reduce your stake and does not require the unstaking exit period. Partial reward claims are not supported.

For validator owners, this balance includes both unclaimed commission and rewards from self-stake. Neither is automatically transferred to the owner wallet. See [Commission and Rewards](https://docs.pharos.xyz/native-staking/validator-guide/commission-and-rewards.md) for querying, claiming, and compounding examples.

Rewards already included in a withdrawal request are claimed with that request after it unlocks. They are no longer part of the pool's separately claimable reward balance.

Existing rewards can still be claimed when a validator is no longer active. Reward claims are unavailable while the staking contract is paused; already unlocked stake withdrawals remain claimable.

## Compound Rewards

`compoundRewards(poolId)` adds available rewards to pending stake in the same pool. The compounded amount becomes effective at the next epoch, allowing it to earn further rewards. Compounding does not require unstaking or moving PROS through your wallet.

To compound, you need effective stake and available rewards, with no stake awaiting activation and no outstanding withdrawals in that pool. Compounding is limited by the pool's remaining capacity; any excess rewards remain unclaimed.

**Auto-compound** allows an authorized operator to perform this action for you. The authorization is specific to your pool and has an expiry time. It only permits compounding your rewards into your own position; it does not allow the operator to withdraw your principal or rewards. You can revoke it.

Each automatic compound transaction follows the same activation and capacity rules as manual compounding.

## Commission and Estimated Returns

Check the validator's current commission before staking. Commission applies to rewards, not the amount you deposit. Rate changes follow an epoch delay; a pending rate is not the current rate.

APR is an estimate, not a fixed return. Actual rewards depend on network rewards, effective stake, validator participation, and commission. Compounding can increase effective stake over time, but rewards are not automatically compounded without a successful compound transaction.


---

# 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/rewards-and-claiming.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.
