> For the complete documentation index, see [llms.txt](https://docs.warpgate.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.warpgate.pro/product/warpgate-dex/token-swaps-on-warpgate.md).
# Token Swaps on WarpGate
Dynamic Fee Structure: Optimized for Seamless Trading
WarpGate introduces a **dynamic liquidity pool** system, offering flexible fee tiers ranging from **0.1% to 1%**. This structure ensures efficient token swaps while balancing the needs of traders and liquidity providers (LPs).
* **70% Fee Redistribution** – Liquidity providers **earn more** with flexible fee structures.
***
#### Adaptive and Resilient
WarpGate's fee structure adapts to market conditions and user feedback, creating a **dynamic and competitive trading environment**. While initial liquidity dispersion may occur, convergence is anticipated as the market establishes its equilibrium.
***
#### Mitigating Impermanent Loss
The tiered fee model minimizes risks for LPs by aligning fees with market volatility. High-risk pairs are incentivized with higher fees, fostering **healthy liquidity provisioning** across the platform.
---
# 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.warpgate.pro/product/warpgate-dex/token-swaps-on-warpgate.md?ask=&goal=
```
`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.