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

# NFT staking

NFT staking lets holders stake ERC-721 tokens and earn an ERC-20 reward over a fixed window.

## Who it is for

* **Creators** who want to reward holders of a collection with a token.
* **Holders** who want to earn that token for staking their NFTs.

Step-by-step instructions are on [How to stake](https://polydash.gitbook.io/polydash-docs/polypad/how-to-stake.md). On the site, open [polypad.family/stake](https://polypad.family/stake), choose **NFTs**, pick a pool, and check the collection and reward token addresses before you stake. You can withdraw NFTs at any time.

## How it works

`NftStakingFactory` deploys one `NftStakingPool` per collection and reward token.

{% stepper %}
{% step %}

### Create a pool

The creator picks a collection, a reward token, a start and end time, and funds the pool. Any contract that reports ERC-721 support through ERC-165 can get a pool.
{% endstep %}

{% step %}

### Stake NFTs

Holders deposit their NFTs. Rewards stream across the window `[start, end)`.
{% endstep %}

{% step %}

### Claim or withdraw

Holders claim rewards and withdraw NFTs at any time. `emergencyWithdraw` makes no reward-token calls, so a broken reward token cannot trap an NFT.
{% endstep %}

{% step %}

### Top up

`fund()` can raise the reward rate over the remaining window. It cannot extend the window or dilute existing stakers.
{% endstep %}
{% endstepper %}

## Boosts

A boosted pool (`createBoostedPool`) adds optional multipliers.

| Boost                                                         | Limit                                  |
| ------------------------------------------------------------- | -------------------------------------- |
| Loyalty tiers, by continuous stake time                       | Up to 4 tiers, up to a 3.0x multiplier |
| Set bonus, for wallets holding a minimum count of staked NFTs | Up to +50%                             |

## Key properties

* Fee-on-transfer aware: funding credits the amount actually received.
* Each pool holds only its own collection and reward token, so a hostile collection is contained to its own pool.
* Unallocated rewards (zero-staker periods, rounding dust, forfeited emergency rewards) can be recovered by the pool creator after the end. Rewards owed to stakers cannot.

## Contract

NftStakingFactory: [`0x827b9BB6a176D13Ea7E05b8e5891c8040cb822B1`](https://robinhoodchain.blockscout.com/address/0x827b9BB6a176D13Ea7E05b8e5891c8040cb822B1) (Sourcify exact match)

## Risks

Pool terms are set by the pool creator. Check the collection and reward token addresses. Rewards depend on the reward token, which can lose value. The contracts are **Not audited.**


---

# 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://polydash.gitbook.io/polydash-docs/polypad/nft-staking.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.
