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

# DexSwap

Liquidity for the DexFi ecosystem

dexSWAP is the swap that provides the liquidity that backs the DexFi ecosystem. Presently, it exists only on Arbitrum.

### MEV Bot Protection

dexSWAP is protected from MEV bots meaning assets can safely be traded on dexSWAP without being sandwiched

### Only Protocol Owned Liquidity (POL)

The liquidity on dexSWAP is 100% protocol owned and as such there is no farming token for dexSWAP

### Swap Fees

The swap fees on dexSWAP are 0.3% and 100% of this goes to the protocol. None of the fees go to liquidity providers.

### Hosting Liquidity on dexSWAP

At this point in time, DexFinance is not looking to host liquidity for other projects


---

# 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.dexfi.com/dexfi-products/dexswap.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.
