> 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-6-and-roadmap.md).

# Phase 6 multi-asset funds

Tokenized Funds V2 (Phase 6) is **live** on Robinhood Chain. The factory is deployed, it has creation and runtime bytecode, Sourcify records an exact match under the contract name `FundFactoryPhase3V2`, and [polypad.family/funds](https://polypad.family/funds) lists it as Tokenized Funds V2, Phase 6.

The factory was deployed on November 10, 2026 at 7:16 AM PT (America/Los\_Angeles) in transaction [`0x27d76e70d63541618f3d6d672be292bab752c7b61cec77cf9c7d0ef00557a314`](https://robinhoodchain.blockscout.com/tx/0x27d76e70d63541618f3d6d672be292bab752c7b61cec77cf9c7d0ef00557a314) (block 110978576, nonce 47) by `0x9a21c75aC263cC43125E70200636f6397f8776d0`. As of November 14, 2026, `allFundsLength()` is 0: the factory has not created a fund yet.

The contracts are **Not audited.** Sourcify verification is a bytecode check, not a review. The Phase 6 sources are on Sourcify and are not yet recorded in `docs/DEPLOYMENTS.md` on the repository's main branch.

## What Phase 6 adds

A Phase 6 fund still copies a locked strategy template. In addition, the manager can propose new assets in public and add them to that fund's mandate after a wait.

* A fund's mandate can list **up to 16 assets** (`MAX_ASSETS`).
* The manager calls `proposeAsset` with a per-asset cap, a short reason, and a write-up URI. After `PROPOSAL_DELAY` (**2 days**, 172,800 seconds), the manager can execute the proposal.
* The shared asset allowlist has the same live wait: `delay()` is **2 days**. The two waits run in parallel, and both must finish before the fund can buy the new asset. The allowlist owner cannot set `delay` shorter than **1 day** (`MIN_DELAY` = 86,400 seconds).
* A newly proposed asset defaults to a **30%** position cap (`DEFAULT_ASSET_CAP_BPS` = 3,000). The proposal can set a different cap, up to 100%.
* Templates 2 through 5 (Polydash Growth Fund variants) set their template-asset cap at **80%** (`maxPositionBps` = 8,000) for the official POLYDASH token. That cap applies to the template asset. Later proposals still default to 30% unless the proposal sets another value.
* Holders can exit during the wait.
* Swaps go through allowlisted Uniswap adapters, called by `FundSwapFacetPhase3V2`. The live allowlist has two routers: `UniswapV3RouterAdapter` and `UniswapV4RouterAdapter`.

There is no separate `FundAllowlistPhase6` contract. Phase 6 reuses the live Phase 2 `FundAllowlist`.

## Verified addresses

All addresses are on Robinhood Chain (chain ID 4663).

| Contract                                          | Address                                                                                                                                  | Sourcify                                |
| ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- |
| `FundFactoryPhase3V2` (Tokenized Fund factory V2) | [`0xe50Da719947E83f316977d9c425DF95672E7B27e`](https://robinhoodchain.blockscout.com/address/0xe50Da719947E83f316977d9c425DF95672E7B27e) | Exact match, recorded November 10, 2026 |
| `FundSwapFacetPhase3V2`                           | [`0x7dC767E1D0B0AC89282cB72a784174Ce29CdDaC7`](https://robinhoodchain.blockscout.com/address/0x7dC767E1D0B0AC89282cB72a784174Ce29CdDaC7) | Exact match, recorded November 10, 2026 |
| `FundAllowlist` (reused from Phase 2)             | [`0x7A42Dc64f77711EA20d163eFB1B9FaCCC2cA2c19`](https://robinhoodchain.blockscout.com/address/0x7A42Dc64f77711EA20d163eFB1B9FaCCC2cA2c19) | Exact match                             |
| `StrategyTemplate` (reused from Phase 3)          | [`0xb2a958a9779E02764dE006C8aeEbc36174E2E3Ba`](https://robinhoodchain.blockscout.com/address/0xb2a958a9779E02764dE006C8aeEbc36174E2E3Ba) | Exact match                             |
| `UniswapV3RouterAdapter`                          | [`0xA5187f8e56Dd0784624D833CEE3bF6f2Aa5E7581`](https://robinhoodchain.blockscout.com/address/0xA5187f8e56Dd0784624D833CEE3bF6f2Aa5E7581) | Exact match                             |
| `UniswapV4RouterAdapter`                          | [`0x25eb10357213f17b2862b54773287fccfeb92b7a`](https://robinhoodchain.blockscout.com/address/0x25eb10357213f17b2862b54773287fccfeb92b7a) | Exact match, recorded November 10, 2026 |
| WETH                                              | [`0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73`](https://robinhoodchain.blockscout.com/address/0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73) | —                                       |

The factory owner and fee recipient is `0x9a21c75aC263cC43125E70200636f6397f8776d0`.

The factory also reports these deployer helpers, which have bytecode on-chain. They were not verified on Sourcify when this page was written:

| Role              | Address                                                                                                                                  |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| `nftDeployer()`   | [`0xf4262dB48C1301E8270f8e0a6B38f5b2fea7A550`](https://robinhoodchain.blockscout.com/address/0xf4262dB48C1301E8270f8e0a6B38f5b2fea7A550) |
| `vaultDeployer()` | [`0x111b0DAc80f056B21C786eb69a046E0F6e415486`](https://robinhoodchain.blockscout.com/address/0x111b0DAc80f056B21C786eb69a046E0F6e415486) |

## Allowlist and adapters

The shared allowlist currently permits WETH, the official POLYDASH token, and other assets that have been added through its public proposal process. The list can change. Quote asset is WETH. The allowlist is not paused.

Swaps must use an allowlisted router. The two live routers are the Uniswap V3 and Uniswap V4 adapters above. The facet wraps or unwraps WETH when needed, checks the fund's per-asset and per-trade caps, and records the trade on the vault.

## Not in scope

Stock tokens and similar regulated instruments are not part of the shipped funds. Any such work needs legal review before it is built.

## Related

* [Polypad Funds](https://polydash.gitbook.io/polydash-docs/polypad-funds.md)
* [Strategy templates](https://polydash.gitbook.io/polydash-docs/polypad-funds/strategy-templates.md)
* [Fund contracts](https://polydash.gitbook.io/polydash-docs/polypad-funds/fund-contracts.md)
* [Fund share NFTs and carry tokens](https://polydash.gitbook.io/polydash-docs/polypad-funds/fund-share-nfts-and-carry.md)

## Risks

New contracts add new risk. A manager still decides what the fund buys, within the template and allowlist rules. You could lose some or all of the ETH you put in. The Phase 6 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-6-and-roadmap.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.
