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

# A Unique Fee Structure

Overview of Multiswap's Unique Fee Implementation

Multiswap's introduction of an innovative tiered fee system, akin to major centralized exchanges like Coinbase, marks a groundbreaking shift in AMM fee structures. Unlike conventional AMMs that apply a uniform fee across the entire pool and often support only two tokens per pool, Multiswap's approach allows each asset within the pool to have an individualized fee structure. 

By tailoring fees for each asset within the unified pool, Multiswap offers a fee structure that can reward high-volume traders and liquidity providers.

Traders with higher trading volumes are rewarded with fee discounts, encouraging them to conduct more transactions on the platform and increase LP profitability. 

Below is the fee matrix for the Large Cap Crypto Pool:

| Asset  | Fee     |
| ------ | ------- |
| WAVAX  | 0.2500% |
| USDC   | 0.0050% |
| USDt   | 0.0050% |
| EUROC  | 0.0100% |
| USDC.e | 0.0050% |
| USDT.e | 0.0050% |
| DAI.e  | 0.0150% |
| WETH.e | 0.2000% |
| wBTC.e | 0.2000% |
| BTC.b  | 0.2000% |


---

# 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://docs.caval.re/overview/a-unique-fee-structure.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.