> For the complete documentation index, see [llms.txt](https://climbtoken.gitbook.io/climb-token/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://climbtoken.gitbook.io/climb-token/how-does-climb-work/penalty-fees-and-rewards.md).

# Penalty fees and rewards

## Penalty fee

Each sell transaction on our platform will be penalized with a 10% fee. This in order to encourage users to holding, avoid massive sales and speculators. Making the price of CLIMB increase. Also a 2% penalty fee for those who unstake within 3 days. This fee will be distributed to those who still hold CLIMB, increasing their holdings. (Rewards).

5% redistributed to all existing holders. \
5% (50/50) of which is sold by the contract into BNB and for BUSD dividends

## Rewards 

To give the best performance to our users, we will distribute the fees and profits generated by our protocol and platform. In dividends, tokens, buybacks and token burnings.


---

# 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://climbtoken.gitbook.io/climb-token/how-does-climb-work/penalty-fees-and-rewards.md?ask=<question>&goal=<endgoal>
```

`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.