> For the complete documentation index, see [llms.txt](https://pool-party-xyz.gitbook.io/pool-party-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pool-party-xyz.gitbook.io/pool-party-docs/pool-party-v2-docs/resources/faq.md).

# FAQ

**What is Pool Party?** An on-chain collective asset management platform. A manager creates a pool with a strategy, and users take part while keeping self-custody.

**Does Pool Party hold my assets?** No. Pool Party is non-custodial. Your position is tied to your wallet; neither the manager nor Pool Party can take or freeze your assets.

**Do I receive a share token?** No. The share is internal to the contract and accessed only by your wallet.

**What are the fees?** A performance fee (from 10% to 90%, set by the manager, on gains) and a swap fee (to convert USDC).

**Is Pool Party audited?** Not yet. When an audit happens, it will be published.

**Can I lose money?** Yes. Taking part in a pool carries risk, including total loss. See Understand risk and the Disclaimer.

**Who can be a manager?** Anyone. Access is permissionless, with optional social verification.

**Does Pool Party recommend managers or strategies?** No. Pool Party does not endorse any manager or strategy.

**Which networks does Pool Party run on?** v1 runs on Arbitrum, Base, and Polygon. v2 networks are still to be announced.

**How do withdrawals work?** Through your wallet, in USDC or in the strategy's assets (in kind). See Withdraw.

**What is Rubber Rush?** Pool Party's points program. You earn Quacks for using the platform. See Rubber Rush.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://pool-party-xyz.gitbook.io/pool-party-docs/pool-party-v2-docs/resources/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.