# Protocol Fee

## Bridge Swap

| Bridge Type          | Fee Structure                                                                  |
| -------------------- | ------------------------------------------------------------------------------ |
| Liquidity Bridge     | Base fee (0.005ETH per swap, 0.005 BNB per swap) + 0.08% of the bridged tokens |
| Mint and burn Bridge | Base fee (0.005ETH per swap, 0.005 BNB per swap)                               |

Chainswap is not one of the "no fee" exchanges, but charge  0.08% per transaction for makers on the liquidity bridge. Regardless of whether you compare to DEXs or centralized exchanges, these fees are above industry average. In addition, Chainswap charges a base fee of 0.005ETH per bridge transaction to prevent abuse of bridge.

{% hint style="info" %}
Liquidity Bridge e.g. I swap 10000 USDT from ETH to BSC; I need to pay 10000\*0.08%=8 USDT and 0.005 ETH.
{% endhint %}

{% hint style="info" %}
Mint and Burn Bridge e.g. I swap 10000 TOKEN from ETH to BSC; I need to pay 0.005 ETH
{% endhint %}

## Bridge Deployment

The permission-less deployment on ChainSwap charges a fee of 0.3ETH for each token. (Break down: The mapping contract deployment fee is 0.1ETH and the factory contract deployment fee is 0.2 ETH). 

## Where does the fee go?

The fees will go to the contract which are managed by the ChainSwap Dao. Fees will be used to buy back TOKEN from the market. We will make announcement with prove of purchase during each period of TOKEN buy back.


---

# Agent Instructions: 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:

```
GET https://docs.chainswap.com/protocol-fee.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.