> 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/create-a-fund.md).

# Create a fund

A manager creates a fund the way a creator creates an NFT collection. This page covers what a manager sets and the steps to start a raise.

## Who it is for

Managers who want to pool ETH from other people under rules that holders can read in code.

## What a manager sets

For the original raise-only factory (Phase 1a), a manager sets:

| Setting                | Rule                                                                                                                    |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Name                   | 1 to 64 bytes                                                                                                           |
| Symbol                 | 1 to 16 bytes                                                                                                           |
| Image URI and base URI | Each up to 512 bytes. The base URI can change until a share is minted, then it is fixed                                 |
| `mintPrice`            | 0.00001 ETH to 100 ETH. Buyers pay exactly `qty * mintPrice`                                                            |
| `raiseCap`             | Sets `maxSupply = raiseCap / mintPrice`, rounded down. `maxSupply` must be 1 to 10,000                                  |
| `entryFeeBps`          | Optional, 0 to 500 (0% to 5%). The manager's fee on mint ETH                                                            |
| `minSkinBps`           | Optional. `0` selects 500 (5%). Otherwise 500 to 10,000. The required units are `ceil(maxSupply * minSkinBps / 10,000)` |

From Phase 2, a fund also has a raise deadline of 1 hour to 30 days. From Phase 3, a fund is created from a [strategy template](https://polydash.gitbook.io/polydash-docs/polypad-funds/strategy-templates.md), which supplies the mandate, asset list, caps, performance fee, drawdown brake, and skin-lock duration.

## Steps

{% stepper %}
{% step %}

### Choose a template

Pick a published strategy template. The fund copies the template's values. The manager cannot override them.
{% endstep %}

{% step %}

### Create the fund

The wallet that sends `createFund` becomes the manager. The factory deploys one vault and one share contract for the fund.
{% endstep %}

{% step %}

### Mint the skin shares

The manager must mint the required number of units, paying `mintPrice` like anyone else, before another wallet can mint. After that, public minting is open. The requirement is to mint, not to keep holding.
{% endstep %}

{% step %}

### Raise

Mint ETH goes straight into the vault in the same transaction. It is not sent to the manager's wallet. The raise closes when the cap or `maxSupply` is reached, or at the deadline.
{% endstep %}
{% endstepper %}

## Where the money goes

* Mint ETH is forwarded to the vault.
* The 0.2% protocol fee and the manager's entry fee are rounded down separately out of the gross amount. The remainder is `principal`.
* The manager can pull accrued entry fees to a payout wallet. That pull never sends principal.
* Direct ETH transfers to the vault revert.

## Clone an existing mandate

Phase 4 adds **Copy this mandate**, which returns the `createFund` call for an existing fund's template. The wallet that sends the call becomes the manager. See [Phase 4 add-ons](https://polydash.gitbook.io/polydash-docs/polypad-funds/phase-4-add-ons.md).

## Risks

A manager decides what the fund buys within the template's rules. Investors can lose some or all of their ETH. The contracts are **Not audited.** See [Fund fees](https://polydash.gitbook.io/polydash-docs/polypad-funds/fund-fees.md) and the [Risk disclosure](https://polydash.gitbook.io/polydash-docs/security-and-risk/risk-disclosure.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/polypad-funds/create-a-fund.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.
