> For the complete documentation index, see [llms.txt](https://trufflefinance.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trufflefinance.gitbook.io/untitled/truffle-token/trading-fees-explained.md).

# Trading Fees Explained

💵Buy FEE 14%

* 🏦 6%Risk Insurance Fund
* 🍬 2% Truffle Bank
* 🔥 1% Bonfire
* ⚡️4% Automatic LP
* 🏫 1% Treasury

💵SELL FEE 16%

* 🏦6%Risk Insurance Fund
* 🍬2% Truffle Bank
* 🔥 1% Bonfire
* 🎨 2% Nfts Owners Rewards
* ⚡️4% Automatic LP
* 🏫 1 % Treasury

**Placement:** 

* Liquidity Pool **-** Trading fees go to backing the liquidity of the $TRUFFLE/BNB pair on PancakeSwap ensuring an ever-increasing collateral value of $TRUFFLE.  
* TRUFFLE Risk Insurance Fund (RIF)**-** Trading fees are stored in the RIF which helps sustain and back the staking rewards provided by the positive rebase.
* The TRUFFLE Treasury **-** Trading fees go directly to TRUFFLE Treasury which supports the RIF and provides a marketing budget for $TRUFFLE and funds new product development.
* The Bonfire **-** 1% of all $TRUFFLE traded are burnt in the bonfire. The more that is traded, the more get put into the hole causing the black hole to grow in size, larger and larger through self-fulfilling auto-compounding which in return acts to reduce the circulating supply of $TRUFFLE and keeps the $TRUFFLE project stable.


---

# 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://trufflefinance.gitbook.io/untitled/truffle-token/trading-fees-explained.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.