> For the complete documentation index, see [llms.txt](https://docs.pstake.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pstake.finance/pstake-staking/pstake-staking-details/staking-overview.md).

# Staking Overview

To participate in pSTAKE Staking, users must deposit PSTAKE into the staking module.

All staking and unstaking actions are conducted on the Base and can be executed anytime. Before staking, participants will be required to bridge PSTAKE tokens to the Base network. To learn how to bridge to Base, please [follow this guide](https://blog.pstake.finance/2024/05/16/how-to-bridge-pstake-to-base-chain-user-guide/).

{% hint style="info" %}
NOTE: There is a minimum staking amount of 100 $PSTAKE.
{% endhint %}

Rewards are distributed across consecutive two-week season epochs.

Immediate reward generation occurs upon staking, but unstaking during a season forfeits a portion of the rewards generated.

Users will not be required to unstake after one season ends and another begins.

It is important to note that each season will have a staking cap, dictating the maximum amount of PSTAKE that can be staked. The Staking Cap will be announced before each season starts, and users will need to be quick to participate in that particular season.<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pstake.finance/pstake-staking/pstake-staking-details/staking-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.