# Development Goals

<figure><img src="/files/JkqZ2hxQGuUOTFkX5tuq" alt=""><figcaption></figcaption></figure>

### 2024 Q1

* February: OTC officially launched, enabling users to trade freely.
* March: TBC officially on-chain, whitepaper released, website opened, disclosure of TBC's black hole address and distribution addresses for increased transparency, expansion of the initial 100,000 seed user players.

### 2024 Q2

* April: First blockchain game project contracted, releasing the first blockchain game. Initiate TBC community ecosystem development. Global promotion kickoff with the release of the first promotional video.
* May: Introduction of chain game NFT collaboration features, expanding consumer investment options. Commence TBC staking mining.
* June: Mainnet officially launched, providing higher security and scalability for the TBC ecosystem. Expand the second batch of 200,000 core user players.

### 2024 Q3

* July: Second blockchain game project launched, operating on a dedicated TBC public chain.
* August: All systems officially migrated to the TBC public chain, ensuring complete decentralization.
* September: TBC officially on decentralized exchanges, providing users with more trading options and liquidity. Expand the second batch of 500,000 core user players.

### 2024 Q4

* October: Release developer documentation and collaborate with more chain game developers.
* November: Encourage more developers to develop updated chain game projects.
* December: Global launch of the "TBC Annual Awards," rewarding active community members, players, and developers. Announcement of TBC Annual Ambassadors. Achieve 1 million user player milestone.


---

# 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://tourbillion.gitbook.io/docs/development-planning/development-goals.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.