> For the complete documentation index, see [llms.txt](https://battlestakes.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://battlestakes.gitbook.io/whitepaper/tokenmomics/fees.md).

# Fees

#### Buy fees will be 16% and will be composed of the following:

·        Liquidity Pool (4%)

·        Insurance Fund (4%)

·        Treasury (2%)

·        Burn / Fire Cauldron (2%)

·        $ARENA Coin Fund (2%)

·        Winners Circle Fund (1%)

·        Referral Fund (1%)

#### Sell fees will be 18% and will be composed of the following:

·        Liquidity Pool (4%)

·        Insurance Fund (5%)

·        Treasury (3%)

·        Burn / Fire Cauldron (2%)

·        $ARENA Coin Fund (2%)

·        Winners Circle Fund (1%)

·        Referral Fund (1%)

In order to prevent dumping at the launch the initial sell fee will be 30%. Each day the sell fee will reduce by 1% until it reaches 18%. The additional fees collected from this higher tax will be allocated as follows:

•        ¼ to Winners Circle Fund

•        ¼ to Arena Coin Fund

•        ¼ to Liquidity Pool

•        ¼ to Dev & Marketing

&#x20;

There will be a 40% transfer fee on the transfer of $GEN from wallet to wallet.


---

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

```
GET https://battlestakes.gitbook.io/whitepaper/tokenmomics/fees.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.
