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

# Roadmap

## **Q2 2024**&#x20;

* &#x20;August 8 2024: Official Open Beta of TonCapy launched.&#x20;
* &#x20;Idea generation.&#x20;
* &#x20;Establish core team, develop.&#x20;
* &#x20;Launch Telegram Mini App.

## **Q3 2024**

* Implement Spin, Bush,... features to encourage users to participate in daily events.
* Implemented the Tribe feature, to encourage users to participate in creating and developing their own meme community.
* Implement basic marketing strategies.
* Collaborate with many other communities that also have active TMA.
* Collaborate with **Ting Foundation**.
* Discussion on Investment Partnership Program with **UFIN Labs**

## **Q4 2024**&#x20;

* Run a scoring program for users participating in Airdrop.
* Collaborate with CEXs to discuss premarket, listing, ...
* Deploy Airdrop program, distribute tokens to the earliest players.
* Launch **5 launchpad platforms** supporting TonCapy.
* Announce a list of over **10 CEX** listings.
* Reveal backers and investors, including **Ting Foundation**.

## **Q1 2025**&#x20;

* Optimize Spin, Bush, Tribe... features to help users have a better experience.&#x20;
* Continue to expand the community partner network.&#x20;
* Continue to score the activities of users participating in the **next phase of Airdrop**.&#x20;
* Discuss and agree on **new CEX** listing.
* Official **CEX Listings** for **TCapy** token.
* Launch **Ting Market** – NFT Marketplace.
* Issue **Genesis NFTs** for Ting Market.
* Launch **Ting Nect** – Web3 Wallet for Telegram.
* Launch **Ting Studio** – Featuring 20 game projects.
* Launch **Ting Borrow** – A decentralized lending platform supporting multi-ecosystem finance.

## **Q2 2025**&#x20;

* Open **Marketing platform** feature for partners, tribe owners. Apply using **TCapy** token for **payment** and NFT utilities are enabled.&#x20;
* Launching TCapy on **Ethereum**, **TON**, and **Ting** Chain.
* Continue to optimize Spin, Bush, Tribe... features to help users have a better experience. Continue to expand the community partner network.&#x20;
* Continue to score the activities of users participating in the next phase of Airdrop.&#x20;
* Discuss and agree on new CEX listing.
* Launch **Mainnet Ting Chain** and its first DEX platform.
* Launch **Ting Depin** – Decentralized Physical Infrastructure Network.

## **Q3 - Q4 2025**&#x20;

* TonCapy continues to go to market.&#x20;
* Continue to improve old features and update many new features to help promote active user interaction every day.&#x20;
* Continue to expand the community partner network.&#x20;
* Continue to score the activities of users participating in the next phase of Airdrop.
* Launch **200 projects** on the **Ting Eco** via TonCapy’s **DAO Community Platform**, supported by **Ting Foundation** and backed by **10 major CEXs**.


---

# 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://toncapy.gitbook.io/toncapy/roadmap.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.
