> 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.md).

# Polypad Funds

Tokenized funds on Robinhood Chain. People buy equal shares with ETH, and a manager invests under rules locked at creation.

**Polypad Funds** ([polypad.family/funds](https://polypad.family/funds)) lets a manager start a tokenized fund. People buy shares with ETH, the ETH sits in the fund's vault, and the manager invests within rules that are fixed when the fund is created. Holders can leave through the contract.

{% hint style="warning" %}
**Not audited.** These contracts have not had a formal outside review. You could lose some or all of the ETH you put in. Only put in what you can afford to lose.
{% endhint %}

## The idea

* Each **share is an ERC-721 NFT**. Every share is one equal unit of the fund. A wallet's slice of the fund is its share count divided by the shares minted.
* The **NFT is the ownership claim**. Listings, wallets, and locks all read it. They do not replace `exit` or `refund`.
* **The manager does not hold the money.** There is no function that sends principal to the manager.
* **Rules are locked at creation.** A fund copies its strategy template, and the manager cannot pass different values.

## Who it is for

* **Managers** who want to pool ETH under visible rules.
* **Investors** who want to hold a share of a fund and can leave on their own terms.

## How a fund works

```mermaid
flowchart LR
  A[Manager creates fund] --> B[Manager mints required shares]
  B --> C[Public raise]
  C -->|Cap or deadline| D{Raise outcome}
  D -->|Filled| E[Investing]
  D -->|Missed deadline| F[Failed: refund]
  E --> G[Holders exit pro rata]
```

1. The manager creates a fund from a template. See [Create a fund](https://polydash.gitbook.io/polydash-docs/polypad-funds/create-a-fund.md).
2. The manager mints a required share of the supply, paying like anyone else. This is the skin requirement.
3. The public raise opens. See [Invest, exit and refund](https://polydash.gitbook.io/polydash-docs/polypad-funds/invest-exit-refund.md).
4. The manager invests within the template's rules. See [Strategy templates](https://polydash.gitbook.io/polydash-docs/polypad-funds/strategy-templates.md).
5. Holders can exit at any time and receive a pro-rata share of what the vault holds.

## Phases

| Phase | What it adds                                                                                                                  | Status                                                                                                                                                                                                                                                   |
| ----- | ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1a    | Raise and mint. Equal ERC-721 units at a fixed ETH price. No investing                                                        | Deployed                                                                                                                                                                                                                                                 |
| 2     | Raise deadline, refund, exit, an asset allowlist, swaps through allowlisted routers, NAV from price feeds                     | Deployed                                                                                                                                                                                                                                                 |
| 3     | Strategy templates, performance fee above a high-water mark, drawdown brake, manager skin lock                                | Deployed                                                                                                                                                                                                                                                 |
| 4     | Clone a mandate, expiring trading agent, season cards, NAV bids, per-share wallets                                            | Deployed. See [Phase 4](https://polydash.gitbook.io/polydash-docs/polypad-funds/phase-4-add-ons.md)                                                                                                                                                      |
| 5     | Secondary listings, on-chain share art, conviction locks, carry token, nav-floor exit                                         | Deployed. See [Phase 5](https://polydash.gitbook.io/polydash-docs/polypad-funds/phase-5-add-ons.md)                                                                                                                                                      |
| 6     | Tokenized Funds V2 factory with public asset proposals, custom lists of up to 16 assets, Uniswap adapters, and per-asset caps | Live. The factory is deployed, verified, and listed on the Polypad Funds page. No Phase 6 fund had been created as of November 14, 2026. See [Phase 6 multi-asset funds](https://polydash.gitbook.io/polydash-docs/polypad-funds/phase-6-and-roadmap.md) |

Each phase is a separate set of contracts. A later phase does not modify an earlier deployed contract.

## Guides in this section

* [Create a fund](https://polydash.gitbook.io/polydash-docs/polypad-funds/create-a-fund.md)
* [Invest, exit and refund](https://polydash.gitbook.io/polydash-docs/polypad-funds/invest-exit-refund.md)
* [Strategy templates](https://polydash.gitbook.io/polydash-docs/polypad-funds/strategy-templates.md)
* [Fund fees](https://polydash.gitbook.io/polydash-docs/polypad-funds/fund-fees.md)
* [Drawdown brake and skin lock](https://polydash.gitbook.io/polydash-docs/polypad-funds/drawdown-brake-and-skin-lock.md)
* [Phase 4 add-ons](https://polydash.gitbook.io/polydash-docs/polypad-funds/phase-4-add-ons.md)
* [Phase 5 add-ons](https://polydash.gitbook.io/polydash-docs/polypad-funds/phase-5-add-ons.md)
* [Phase 6 multi-asset funds](https://polydash.gitbook.io/polydash-docs/polypad-funds/phase-6-and-roadmap.md)
* [Fund share NFTs and carry tokens](https://polydash.gitbook.io/polydash-docs/polypad-funds/fund-share-nfts-and-carry.md)
* [Fund contracts](https://polydash.gitbook.io/polydash-docs/polypad-funds/fund-contracts.md)

## Not included

Stock tokens and other regulated assets are not part of the shipped funds. Funds hold ETH, WETH, and assets that a template and an allowlist permit. Anyone planning a fund that holds regulated instruments should get legal advice before launching.


---

# 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.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.
