# CLIMB CONTRACT

**Contract Address:** 

[**https://bscscan.com/token/0x2A1d286ed5edAD78BeFD6E0d8BEb38791e8cD69d**](https://bscscan.com/token/0x2A1d286ed5edAD78BeFD6E0d8BEb38791e8cD69d)

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

0x2A1d286ed5edAD78BeFD6E0d8BEb38791e8cD69d

**(OLD) Contract address used for CLIMB development:** 0x2A1d286ed5edAD78BeFD6E0d8BEb38791e8cD69d

The old contract "0x4945bc280aae4ce44f99ce1e4cbe58421714f45d" was used for necessary tests in the development of farming and staking.

The holders of the old contract already have their tokens in the current contract, they just have to add it to metamask. Like a hardfork.\
\
As indicated to the community, the old token was used solely for the development of CLIMB and its platform. After this the new OFFICIAL optimal contract for the public and our platform: 0x2A1d286ed5edAD78BeFD6E0d8BEb38791e8cD69d


---

# 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/climbcontrack.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.