> 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/invest-exit-refund.md).

# Invest, exit and refund

This page explains how an investor buys a share, leaves a fund, or gets a refund if a raise fails.

## Buy a share

{% stepper %}
{% step %}

### Open the fund page

Check the manager, the template, the fees, the raise deadline, and the contract address.
{% endstep %}

{% step %}

### Mint

Buy one or more shares at the fixed price. You pay exactly `qty * mintPrice`. Each share is an ERC-721 token.
{% endstep %}

{% step %}

### Hold or manage

Your share is your claim. A wallet's slice is `balanceOf(wallet) / totalMinted`.
{% endstep %}
{% endstepper %}

## Fund states

| State                   | Meaning                                                               |
| ----------------------- | --------------------------------------------------------------------- |
| Waiting for the manager | The manager has not yet minted the required units. Others cannot mint |
| Open for investments    | The public raise is open                                              |
| Investing               | The raise is closed and the manager can trade within the rules        |
| Refund available        | The raise missed its deadline                                         |
| Closed                  | The fund has finished                                                 |

## Exit

After the raise closes or investing begins, the current holder of a share calls `exit` and receives a pro-rata share of spendable ETH, WETH, and mandate tokens.

* Pause does not block `exit` or `refund`.
* Native ETH is sent before tokens. If a token transfer fails and the tokens are still in the vault, that share is recorded as owed and can be claimed later with `claimOwed`.
* The last outstanding units receive any rounding dust.
* A fee-on-transfer token is not supported. If a holder would not receive the full amount, the exit reverts.
* A recipient that rejects ETH reverts the exit.

## Refund after a failed raise

If the deadline passes while the fund is still raising, anyone can call `failRaise`. Minting stops, and the manager cannot open investing. The current holder of each share calls `refund` and receives a pro-rata share of spendable ETH.

{% hint style="warning" %}
A refund is the spendable ETH only. It is not a return of the mint price. The 0.2% protocol fee and any entry fee stay withheld and can still be pulled.
{% endhint %}

## Net value

`navPerNft()` is the vault's net value divided by the shares outstanding. It counts ETH, WETH at face value, and each mandate asset at its price feed. A missing, stale, zero, or out-of-bounds feed makes the read revert instead of returning a wrong number. It is a reading, not a market price.

## Risks

Your exit pays what the vault holds at that moment. Asset values can fall. Keep your own record of the fund address. 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/invest-exit-refund.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.
