# CLIMB TOKEN

**Ticker:** CLIMB

![](/files/-Mb9_ypzTB2yD-v9PMMh)

**Contract Address:** <https://bscscan.com/token/0x2A1d286ed5edAD78BeFD6E0d8BEb38791e8cD69d>

**Chain:** Binance Smart Chain (BEP-20)

0x2A1d286ed5edAD78BeFD6E0d8BEb38791e8cD69d

**Total MAX supply:** 625,000&#x20;

**Decimals:** 8

**Not mineable.**

**Dividends:** every 15 days in BUSD

**Enabled for staking and farming**

**Deflationary Mechanics:**

At present:

* [x] With the profits obtained from our platform and fees, CLIMB tokens will repurchased to decrease liquidity exchanges. The repurchased tokens will be burned.
* [x] **Penalty fee:** This fee will be distributed to those who still hold CLIMB, increasing their holdings. and used to burn.\
  10% (Each sell transaction on our platform will be penalized with a 10% fee)\
  5% redistributed to all existing holders.\
  5% (50/50) of which is sold by the contract into BNB and for BUSD dividends
* [x] BuyBacks.
* [x] Team rebuys.
* [x] Team tokens burns.&#x20;
* [x] Constantly burns.
* [x] Withdrawal fee of farming and staking are used to rebuy and burn CLIMB.
* [x] Collection of fees to burn CLIMB, MNTN and MARS.
* [x] Climb NFT (in progress)
* [x] ***We remember that the profits obtained from CLIMB's platform will also be used to burn tokens and raise the price.***

CLIMB is a token based on market supply and demand. The CLIMB  price will rise constantly, thanks to the reduction of the circulation, burning of tokens, and buybacks.


---

# 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://climbtoken.gitbook.io/climb-token/tokenomics/climb-token.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.