> For the complete documentation index, see [llms.txt](https://docs.zest.ac/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zest.ac/fee-structure/overview.md).

# Platform Fees

Zest collects a small protocol fee on every transaction routed through the platform. The fee is paid in **native MON** and deducted atomically in the same transaction — no separate approval needed.

## Fee formula

```
feeUSD  = clamp(volumeUSD × bps / 10000, minFee, maxFee)
feeMON  = feeUSD × 1e18 / monPriceUSD
```

The fee tier (bps, min, max) is set on the ZestFeeCollector contract and can be updated by the protocol. Current parameters are readable on-chain.

## Fee collector contract

All fees flow through:

**ZestFeeCollector**: `0xC732Ac29e12D718407255bD4Be30B51d6b1b2CA3`

[View on Monadscan ↗](https://monadscan.com/address/0xC732Ac29e12D718407255bD4Be30B51d6b1b2CA3)

## How it works

**Standard flow** (most swaps and stakes):

1. You send `fee + action value` to ZestFeeCollector
2. Collector takes the fee, forwards `action value` to the target protocol
3. Protocol executes — output goes directly to your wallet

**2-step flow** (LFJ add/remove liquidity, token→MON swaps):

Some protocols pull ERC-20 tokens via `transferFrom(msg.sender)`. When proxied, `msg.sender` would be the fee collector (which holds none of your tokens), causing the transaction to revert. Instead:

1. **Tx 1:** Pay fee directly to collector
2. **Tx 2:** Call the protocol directly as your own wallet

This is why LFJ liquidity actions show **two wallet prompts** — both are expected.

## Fee-free actions

The following are **not subject to Zest fees**:

* Bridge transactions (providers have their own fees)
* Merkl reward claims
* Portfolio / NFT viewing
* Referral code redemption

## Protocols that collect fees

Kuru · aPriori · Magma · Kintsu · shMonad · Neverland · Curvance · LFJ · Dirol · LeverUp · NadFun · Crystal · Bonad


---

# 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://docs.zest.ac/fee-structure/overview.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.