> 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/phase-5-add-ons.md).

# Phase 5 add-ons

Phase 5 is an add-on for a fund created by `FundFactoryPhase3`. It does not modify the Phase 1a, Phase 2, or Phase 3 contracts. One deployment created `FundPhase5`, and its constructor created the market, share renderer, carry token, conviction lock, and nav-floor queue.

The share NFT remains the ownership claim. These contracts read it. They do not replace `exit` or `refund`.

## Secondary listings

`FundSecondaryMarket` lists one share at a fixed ETH amount.

* `list` leaves the share with the holder. `fill` requires the market to be approved for that share.
* `listEscrow` pulls the share in. `cancel` returns it to the seller.
* After a fill, the seller and any royalty receiver call `withdraw`. The market never pushes ETH during the transfer.
* A share in a conviction lock cannot be listed. A skin-locked share cannot be listed.
* A listing does not change vault fee balances or the number of outstanding shares, because it does not mint and does not call `exit`.

## Share art

`FundShareRenderer.tokenURI(nft, tokenId)` builds the share's image in the contract. The SVG uses `#000000` and `#ffffff` only. It shows the fund name, net value per share, the change versus the stored mint price in basis points, the drawdown brake state (`ON`, `OFF`, `UNSET`, or `UNREAD`), and the conviction-lock tier (`0`, `30`, `90`, or `180`).

The figures are vault readings. They are not a quote of what a buyer will pay. A feed that cannot be read is labeled unavailable.

## Conviction locks

`FundConvictionLock.lock` pulls one share for **30, 90, or 180 days**. Until `unlock`, the holder cannot transfer, list, or exit with that share. `unlock` reverts before expiry, and only the recorded holder can call it. There is no payment for locking.

Send the share only through `lock`. A plain `transferFrom` into the lock does not record a holder.

## Carry token

`FundCarryRights` mints one ERC-721 per fund when the manager calls `arm`. The vault's `payoutWallet` must already point at this contract. ETH the vault then sends there is credited to the current carry-token holder, who calls `claim`.

* While routed here, both entry fees and performance fees that the manager pulls are credited to the carry holder. Protocol fees still use the factory fee recipient.
* The manager can point `payoutWallet` somewhere else later. `routed` reports whether it still points here. Amounts already received stay with the carry holder.
* Transfer of the carry token reverts while the vault is raising, while the drawdown brake is on, or while the brake cannot be read.
* The token does not promise a payment.

## Nav-floor exit

`FundNavFloor` queues one share for one day, then calls the share's `exit` (or `refund` after a failed raise). The holder can `cancel` and take the share back.

* `redeem` has no owner and no pause. It runs even when swaps are paused and when the drawdown brake is on.
* Assets are forwarded in kind: ETH, WETH, and mandate tokens, in the amounts the vault already pays.
* If a mandate token does not arrive in full, the redemption reverts and the share stays queued. The holder can cancel and call `exit` on the share.

## Contracts

| Contract            | Address                                                                                                                                  |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| FundPhase5          | [`0x0c98b0E09E4Aa425BD2A85060BE58282E21d0c81`](https://robinhoodchain.blockscout.com/address/0x0c98b0E09E4Aa425BD2A85060BE58282E21d0c81) |
| FundSecondaryMarket | [`0xa2bE46731340A9a5C53DA7D21b6bB8DA3faaC23C`](https://robinhoodchain.blockscout.com/address/0xa2bE46731340A9a5C53DA7D21b6bB8DA3faaC23C) |
| FundShareRenderer   | [`0x6DbC2Df3AE18a610978Ac3c0b765057800CABd0b`](https://robinhoodchain.blockscout.com/address/0x6DbC2Df3AE18a610978Ac3c0b765057800CABd0b) |
| FundCarryRights     | [`0x37d171924Af4072F62ad564C954E977E1D3967c9`](https://robinhoodchain.blockscout.com/address/0x37d171924Af4072F62ad564C954E977E1D3967c9) |
| FundConvictionLock  | [`0x4D216Ad3f28e9eF183483f37b7Ec05b9b46C9B95`](https://robinhoodchain.blockscout.com/address/0x4D216Ad3f28e9eF183483f37b7Ec05b9b46C9B95) |
| FundNavFloor        | [`0x8e4f163e6dCe71Ef1290Ed264c6F11f13F309afb`](https://robinhoodchain.blockscout.com/address/0x8e4f163e6dCe71Ef1290Ed264c6F11f13F309afb) |

Constructor argument: the Phase 3 factory [`0xb9BA453677A6b2C49290CfD4D0713502Ec6bF82B`](https://robinhoodchain.blockscout.com/address/0xb9BA453677A6b2C49290CfD4D0713502Ec6bF82B). Sourcify exact match for all six. Deployed from commit `63d4f745b83d89a2863ff3a82f010ff1da2c501c`.

## Risks

A locked share cannot exit until it is unlocked. A carry token does not promise any payment. 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/phase-5-add-ons.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.
