> 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-4-add-ons.md).

# Phase 4 add-ons

Phase 4 is an add-on for Phase 3 funds. It does not modify the Phase 1a, Phase 2, or Phase 3 contracts. One transaction deployed `FundPhase4`, and its constructor deployed `FundShareAccount`.

The NFT remains the ownership claim. A clone, an agent, a season card, a bid, and a per-share wallet all read that NFT. They do not replace `exit` or `refund`.

## Features

### Clone a mandate

`cloneFromFund` and `cloneFromTemplate` return the live factory address and the `createFund` calldata. The wallet that sends that calldata becomes the manager. `FundPhase4` does not send it, because a wrapper that called `createFund` would become the manager.

### Trading agent for the manager

{% stepper %}
{% step %}

### Name the executor

The manager calls `setExecutor` on the vault with the Phase 4 contract.
{% endstep %}

{% step %}

### Arm an agent

The manager calls `arm` with one agent address, an expiry of at most 30 days, and an optional `maxAmountIn` ceiling.
{% endstep %}

{% step %}

### Agent swaps

`agentSwap` forwards one swap. The vault still enforces the template caps, the allowlist, and the drawdown brake.
{% endstep %}

{% step %}

### Revoke or expire

`revoke` clears the grant at once. After expiry, anyone can `kick` the grant. The vault flag is cleared only by the manager.
{% endstep %}
{% endstepper %}

The agent cannot pull fees, distribute, set the payout wallet, or move the NFT. There is no generic call and no token approval.

### Season cards

Anyone can open a season after investing starts, poke it, and close it after one day. The card stores net value per share at open and close, the change versus the start and the high-water mark in basis points, the largest drop among the readings, and the trade count. The largest drop is only what was read at open, poke, or close. It is not a continuous path.

### NAV bids

`placeBid` escrows the bidder's ETH. The amount must be at least 0.00001 ETH and at or below net value per share, checked again at `settleBid`. The holder must have approved the contract. The bidder can cancel before expiry, and anyone can cancel after expiry. A bid is not a vault exit, and the fund does not pay the seller.

### Per-share wallets

`createShareAccount` creates an ERC-6551 wallet for a share. Only the current NFT owner can call it, and only CALL is allowed. It works while the canonical ERC-6551 registry `0x000000006551c19487814612e58FE06813775758` has code on Robinhood Chain. Exiting or refunding burns the share and freezes the wallet, so move assets out before you exit.

## Contracts

| Contract         | Address                                                                                                                                  |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| FundPhase4       | [`0x3cd372e32Da71321D795a32b244eAa16724531dB`](https://robinhoodchain.blockscout.com/address/0x3cd372e32Da71321D795a32b244eAa16724531dB) |
| FundShareAccount | [`0xC189EBc950D3e3EE7AbBd597060C36DD3E06295E`](https://robinhoodchain.blockscout.com/address/0xC189EBc950D3e3EE7AbBd597060C36DD3E06295E) |

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

## Risks

Per-share wallets freeze when the share is burned. A bid does not pay the fund. 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-4-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.
