> 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-funds/strategy-templates.md).

# Strategy templates

From Phase 3, a fund is created from a **strategy template**. A template is a published, locked set of rules. The fund copies those rules when it is created, and the manager cannot pass looser values.

## What a template sets

| Field                | Meaning                                                                                                                                        |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Mandate hash and URI | A hash of the written mandate, and a link to it                                                                                                |
| Asset list           | The only assets a fund from this template can hold, besides ETH and WETH. An empty list means a quote-only (ETH/WETH) mandate. Up to 16 assets |
| `maxPositionBps`     | Largest share of the fund one asset may reach                                                                                                  |
| `maxTradeBps`        | Largest single trade, as a share of the fund                                                                                                   |
| `maxDeviationBps`    | How far a swap may deviate from the price feed                                                                                                 |
| `hwmFeeBps`          | Performance fee on gains above the high-water mark                                                                                             |
| `maxDrawdownBps`     | Drawdown at which the buy brake turns on. `0` leaves the brake off                                                                             |
| `skinLock`           | Seconds that the manager's required shares cannot be transferred                                                                               |

A published template has no edit function. Templates are published by the owner of the `StrategyTemplate` contract, which is the Polydash fee wallet, so a fund manager chooses from published templates rather than writing their own.

## Published templates

Read from the `StrategyTemplate` contract on Robinhood Chain on November 14, 2026. The contract reported five templates.

| # | Assets            | Max position | Max trade | Max price deviation | Performance fee          | Drawdown brake | Skin lock |
| - | ----------------- | ------------ | --------- | ------------------- | ------------------------ | -------------- | --------- |
| 1 | ETH and WETH only | 30%          | 30%       | 25%                 | 5% above high-water mark | 20%            | 7 days    |
| 2 | POLYDASH          | 80%          | 10%       | 5%                  | 5%                       | 20%            | 30 days   |
| 3 | POLYDASH          | 80%          | 10%       | 5%                  | 0%                       | 20%            | 30 days   |
| 4 | POLYDASH          | 80%          | 10%       | 5%                  | 10%                      | 20%            | 30 days   |
| 5 | POLYDASH          | 80%          | 10%       | 5%                  | 20%                      | 20%            | 30 days   |

The Polypad site names template 2 the Polydash Growth Fund. Check the template on the fund page before you invest, because the fund page is the source of truth for that fund.

## How a Phase 3 fund behaves

* **No edits.** The mandate hash, asset list, position cap, trade cap, deviation cap, performance fee, drawdown brake, and skin-lock duration are copied and fixed.
* **Spendable ETH** excludes entry fees, the 0.2% protocol fee, the performance fee, and ETH reserved for a distribution.
* **Harvest.** `harvest` accrues the performance fee on the gain in net value per share above the high-water mark. The fee stays in the vault for the manager to pull.
* **Distribute.** `distribute` sets aside spendable ETH, one share per outstanding NFT. Holders pull it. An exit pays any unclaimed round before it closes.
* **Net value record.** `NavTape` records net value, the high-water mark, and the drawdown. `Trade` is the blotter event.
* **Swaps.** Swaps run through an allowlist and priced routers. See [Phase 2 controls](#phase-2-controls) below.

## Phase 2 controls

* **Allowlist.** Assets and routers must be on the global `FundAllowlist`. Later additions and removals wait a delay of at least one day. The delay can only be lengthened.
* **Pause.** The manager can pause a fund's swaps right away. Pause does not move balances and does not block `exit` or `refund`.
* **Executors.** The manager can name up to eight executors. An executor can swap. An executor cannot open investing, change the payout wallet, or pull fees.
* **Price checks.** `minAmountOut` must be above zero, the router must have code, and proceeds that do not reach the vault revert the transaction.
* **Blotter.** `Trade(asset, side, size, price, navAfter)` is emitted for each trade, and the vault keeps the latest 32 trades.

## Risks

A template limits a manager. It does not remove market risk. Feeds can be missing or stale, which makes net value reads revert. 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-funds/strategy-templates.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.
