> 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/polydash-token/buybacks-and-rewards-pool.md).

# Buybacks and rewards pool

Two contracts turn a share of Polypad platform fees into POLYDASH burns and staker rewards. They are deployed on Robinhood Chain and are Sourcify matches. They are **Not audited.**

| Contract             | Address                                                                                                                                  |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| PolydashBuybackVault | [`0x35Ad6AC64fb53ED7154b6e6E0Ef84C6E12d7B193`](https://robinhoodchain.blockscout.com/address/0x35Ad6AC64fb53ED7154b6e6E0Ef84C6E12d7B193) |
| PolydashRewardsPool  | [`0x608d106Bb58A804fcd45823e0C6087801dee2aCa`](https://robinhoodchain.blockscout.com/address/0x608d106Bb58A804fcd45823e0C6087801dee2aCa) |

## Live configuration

Both launch factories send **40%** of collected platform fees to the vault (`buybackEnabled` is true and `buybackBps` is 4,000 on the current factory and the earlier factory). Of each buy, **62.5%** is burned and **37.5%** is held for stakers. If a buy runs, that makes **25%** of platform fees go to burns and **15%** to stakers. The factory-side setting is controlled by the fee wallet and can be changed. NFT and staking fees have no on-chain split; the Polypad buybacks page states that 40% of those fees is sent to the vault manually.

{% hint style="warning" %}
The vault and rewards pool are deployed and verified. As of November 14, 2026, the vault held **0 ETH** and **0 POLYDASH**, `totalBurned()` was 0, and the Polypad buybacks page listed no buybacks. That is why the page shows "Next step: Not live". Buybacks are not promised. They depend on fees being collected into the vault and on someone calling the capped buy.
{% endhint %}

## How a buy works

{% stepper %}
{% step %}

### Record a price

Anyone calls `observePrice()`.
{% endstep %}

{% step %}

### Buy 5 to 60 minutes later

Anyone calls `buy()`. It runs only if the pool price is within 2% of the recorded price, spends at most `maxBuyEth`, waits 10 minutes between buys, and enforces a minimum output.
{% endstep %}

{% step %}

### Split the output

The swap output is split in the same transaction: the burn share goes to `0x000000000000000000000000000000000000dEaD`, and the rest stays in the vault for stakers.
{% endstep %}
{% endstepper %}

## Deployed parameters

| Parameter                          | Value                           |
| ---------------------------------- | ------------------------------- |
| `maxBuyEth`                        | 0.02 ETH                        |
| `maxSlippageBps`                   | 300                             |
| `maxPoolFeeBps`                    | 200                             |
| `burnShareBps`                     | 6,250                           |
| Cooldown between buys              | 10 minutes                      |
| Price record valid                 | 5 to 60 minutes after recording |
| Rewards target change              | Public 48-hour time lock        |
| Burn held POLYDASH after no target | 30 days                         |
| Pool                               | POLYDASH/WETH on Uniswap V4     |

## Stakers' share

Held POLYDASH can leave the vault in only two ways:

* `releaseToTarget()`, callable by anyone, sends it to the rewards target through `notifyRewardAmount`.
* After 30 days without an active target, `burnHeldStaking()`, callable by anyone, sends it to the burn address.

Only the `targetAdmin` (the Polydash fee wallet) can propose a new rewards target, and it takes effect only after a public 48-hour time lock. It cannot move ETH or POLYDASH anywhere else. The vault has no owner and no withdraw function, and all parameters are immutable.

## POLYDASH rewards pool

* Stake POLYDASH, earn POLYDASH.
* Anyone can add rewards with `notifyRewardAmount`. The total is re-streamed over 30 days.
* Rewards that would accrue while nobody is staked are carried into the next stream.
* No owner, no lock, no fee. You can unstake at any time.
* Rewards vary with fees and can be zero. The pool makes no promise of any return.

## How to stake in the POLYDASH rewards pool

The rewards pool is a single-sided POLYDASH pool. There is no lock and no fee. You can unstake at any time. Rewards vary with fees and can be zero. As of November 14, 2026, the pool held 0 POLYDASH, so there were no rewards streaming.

A single how-to that also covers permissionless token pools and NFT staking is on [How to stake](https://polydash.gitbook.io/polydash-docs/polypad/how-to-stake.md).

{% stepper %}
{% step %}

### Open the pool

Go to [polypad.family/rewards-pool](https://polypad.family/rewards-pool). Confirm the pool address is [`0x608d106Bb58A804fcd45823e0C6087801dee2aCa`](https://robinhoodchain.blockscout.com/address/0x608d106Bb58A804fcd45823e0C6087801dee2aCa) on Robinhood Chain.
{% endstep %}

{% step %}

### Approve POLYDASH

Connect a wallet on Robinhood Chain. Approve the rewards pool to spend the amount of POLYDASH you want to stake. The official token contract is `0x319525528f42167eF7fC18b77b889958080568e4`. Its on-chain symbol is `polydash`.
{% endstep %}

{% step %}

### Stake

Call `stake` (or use the Stake button on the site). You sign the transaction. The pool is non-custodial: only your wallet can later unstake that position.
{% endstep %}

{% step %}

### Claim or unstake

Rewards, when any are streaming, can be claimed at any time. Unstake whenever you want. There is no lock and no unstake fee. `notifyRewardAmount` is how rewards are added; the buyback vault can call this through `releaseToTarget()` after a buy.
{% endstep %}
{% endstepper %}

Permissionless staking pools for other tokens are covered in [Staking pools](https://polydash.gitbook.io/polydash-docs/polypad/staking-pools.md).

## Known limits

* A buy needs two transactions from a caller who pays gas and receives nothing.
* The POLYDASH pool is thin. Buys are capped at 0.02 ETH and can fill partially.
* The 2% band and the observation delay reduce, but do not remove, exposure to price manipulation.
* The fee wallet controls the factory-side buyback setting with no time lock on the factory side.
* Existing V2 staking pools are funded once and cannot be rewards targets.

## Task feed

Open buyback tasks are listed at `GET /api/agents/v1/buyback-tasks`. See [Endpoint reference](https://polydash.gitbook.io/polydash-docs/agents-and-api/endpoint-reference.md).


---

# 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/polydash-token/buybacks-and-rewards-pool.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.
