> 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/owner-capabilities.md).

# Owner capabilities

This page lists what the Polypad factory owner can and cannot do. The factory is `Ownable2Step`, so a transfer of ownership needs the new owner to accept. The owner should be a multisig. `PolydashLaunch`, `PolydashToken`, and `PolydashHook` have no owner at all.

{% hint style="info" %}
**Golden rule.** Every factory setting applies only to launches created after the change. Each launch copies its config at creation and keeps it for life.
{% endhint %}

## What the owner can do

| Function                     | What it does                                                                     | Bounds                                                                                                |
| ---------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| `setAntiSniperConfig`        | Anti-sniper fee, decay time, wallet-cap window, and cap size for future launches | Fee up to 20%, duration up to 1 hour, cap window up to 100 blocks, cap greater than 0% and up to 100% |
| `setGraduationTarget`        | Graduate on ETH raised or on market cap, for future launches                     | ETH mode 0.1 to 10,000 ETH. Market-cap mode greater than 0 and up to 10,000,000 ETH                   |
| `setBuybackConfig`           | Send a share of **platform** fees to a buyback target                            | Up to 100% of platform fees. Never touches creator fees                                               |
| `setTradingRewardsPool`      | Destination of bought-back POLYDASH                                              | Zero address disables the buyback path                                                                |
| Fee wallet change            | Change the platform fee wallet                                                   | 48-hour time lock. Zero address rejected                                                              |
| `setHook`                    | Hook used by future launches                                                     | The hook must report this factory                                                                     |
| `setPostGraduationSellSpike` | Optional decaying sell surcharge after graduation, donated to locked liquidity   | Up to 10%, up to 1 hour. Off by default                                                               |

`collectPlatformFees` is permissionless. Funds can only go to the configured fee wallet or buyback target.

## What the owner cannot do

* **Change the 0.2% platform fee.** It is a compile-time constant with no setter.
* **Touch creator fees.** The owner cannot change the rate, redirect, pause, or seize them.
* **Change a live launch.** Curve parameters, graduation threshold, anti-sniper config, hook, and fee rate are frozen per launch.
* **Remove or move graduated liquidity.** The hook owns the position and has no removal code path.
* **Mint, pause, blacklist, or tax** a launched token. The token has no owner.
* **Withdraw curve ETH, commitments, or refunds** from a launch.
* **Upgrade anything.** Launch clones point at an immutable implementation.

## If an owner key were compromised

An attacker could start a fee-wallet change (visible for 48 hours), route platform fees into the buyback path, or set harsh but bounded anti-sniper or sell-surcharge settings for **new** launches. Existing launches, creator fees, user funds, and locked liquidity are not affected.

The commit vault has no owner and no admin functions.

Source: `polypad/contracts/docs/OWNER_CAPABILITIES.md`. 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/owner-capabilities.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.
