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

# Treasury rules

Treasury rules let a project hold funds in a per-token treasury where scheduled tasks can only run inside published, on-chain rules and behind a time lock.

## Who it is for

Teams that want to show holders how a treasury will be used, such as buybacks, reward-pool funding, and airdrops.

## How it works

`TreasuryRulesFactory` deploys a `TreasuryRules` implementation in its constructor and creates one EIP-1167 clone per Polypad token, with the token as the salt. Only tokens launched through Polypad are supported.

{% stepper %}
{% step %}

### Create the treasury

The factory creates a clone for the token with its rules.
{% endstep %}

{% step %}

### Queue an action

Withdrawals, rule changes, and airdrops are queued with `queueWithdraw`, `queueRules`, or `queueAirdrop`.
{% endstep %}

{% step %}

### Wait for the time lock

Queued actions wait behind a time lock, then run through `execute`.
{% endstep %}

{% step %}

### Run tasks inside the rules

An operator can run scheduled tasks only within the published rules. The owner can pause the treasury.
{% endstep %}
{% endstepper %}

## Task routes

* Buybacks route through the bonding curve before graduation and through the Uniswap V4 PoolManager after.
* Reward pools are created through `PolydashStakingFactoryV2`.

The agent API lists open treasury tasks at `GET /api/agents/v1/treasury-tasks`. See [Endpoint reference](https://polydash.gitbook.io/polydash-docs/agents-and-api/endpoint-reference.md).

## Contracts

| Contract                       | Address                                                                                                                                  |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
| TreasuryRulesFactory           | [`0x2A06dafEd9A5CaBC7693683E24025f96D7AF656f`](https://robinhoodchain.blockscout.com/address/0x2A06dafEd9A5CaBC7693683E24025f96D7AF656f) |
| TreasuryRules (implementation) | [`0x77Ef2141D3d79e2D2b9a094D2C6d2aab826D4ccb`](https://robinhoodchain.blockscout.com/address/0x77Ef2141D3d79e2D2b9a094D2C6d2aab826D4ccb) |

Both are Sourcify exact matches.

## Note

Routing fees to a project treasury on the Polypad site is a front-end flow and has no dedicated contract.

## Risks

A treasury is only as trustworthy as its published rules and the person who holds the owner role. 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/treasury-rules.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.
