> For the complete documentation index, see [llms.txt](https://zardoz.gitbook.io/zardoz-docs-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zardoz.gitbook.io/zardoz-docs-1/claiming-fees.md).

# Claiming fees

## Claiming fees

Creators and LPs earn different fee streams on Zardoz. Claim from **Portfolio** or **Farm**.

### Fee types

| Type                                  | Who                      | Where to claim                      |
| ------------------------------------- | ------------------------ | ----------------------------------- |
| **Instant / NOXA / Flap launch fees** | Fee recipient / deployer | Portfolio or Farm → **Launch fees** |
| **Bankr / Doppler**                   | Pool initializer         | Hook flush + `collectFees(poolId)`  |
| **trench.today**                      | Registered creator       | trench site + Portfolio panel       |
| **Uniswap V3 LP swap fees**           | LP position owner        | Farm → **My Positions**             |
| **Referral platform fees**            | Ref wallet               | Router `claim()` or ref dashboard   |

***

### Launch fees panel

If you launched a token, eligible positions appear under:

* [Portfolio](https://zardoz.fun/portfolio) → Launch fees
* [Farm](https://zardoz.fun/farm) → Launch fees tab

Connect the wallet that owns on-chain fee rights, then **Claim**.

#### Zardoz Instant — viem example

Only the authorized fee wallet / deployer succeeds:

```typescript
await walletClient.writeContract({
  address: "0xd10bac75248cC975Edc5770a71144a7549594b4e", // Instant locker
  abi: [{
    type: "function",
    name: "collectAndClaim",
    stateMutability: "nonpayable",
    inputs: [{ name: "token", type: "address" }],
    outputs: [],
  }],
  functionName: "collectAndClaim",
  args: [tokenAddress],
});
```

Locker collects accrued Uniswap V3 fees from the locked position NFT and sends ETH/WETH to the configured fee recipient.

***

### Farm — LP position fees

For positions **you** own (NFT in your wallet):

| Action                  | Effect                          |
| ----------------------- | ------------------------------- |
| **Claim**               | Withdraw accrued fees to wallet |
| **Compound**            | Reinvest fees into position     |
| **Add liquidity**       | Increase position size          |
| **Close 25/50/75/100%** | Remove liquidity proportionally |

Out-of-range positions **stop earning** until price re-enters your range or you rebalance.

***

### Launch Agent (token page)

Creators can configure automated fee collection on the token page:

* Visible only to dev wallet / Instant launcher from this client
* Agent params set in factory `create` extras tuple
* Not a substitute for manual claim when agent disabled

***

### External pad specifics

| Pad           | Claim path                         |
| ------------- | ---------------------------------- |
| NOXA          | Locker `collectFees` via Portfolio |
| Flap          | Index Vault `claim`                |
| Bankr         | Doppler hook flush + initializer   |
| trench        | Creator registry at launch         |
| Bags / others | Pad’s own contracts / site         |

Details: External launchpads.

***

### Referral fee claims

Referrers accumulate ETH in `LaunchFeeRouter`:

```typescript
// view
const owed = await publicClient.readContract({
  address: LAUNCH_FEE_ROUTER,
  abi: launchFeeRouterAbi,
  functionName: "claimable",
  args: [referrerAddress],
});

// claim
await walletClient.writeContract({
  address: LAUNCH_FEE_ROUTER,
  abi: launchFeeRouterAbi,
  functionName: "claim",
});
```

See Platform fees & referrals.

Next: Farm · Instant contracts


---

# 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://zardoz.gitbook.io/zardoz-docs-1/claiming-fees.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.