# Roadmap

## Beta :baby\_bottle:

The aim of Beta is to onboard users, strengthen the community and focus on the core gameplay features. During beta the token contract is not yet deployed and crates are free.

{% hint style="info" %}
Only users with certain roles have access during this beta stage. Limited to 5000 players
{% endhint %}

### **Progress:**

* [ ] Testnet Smart Contract
* [ ] Stake Coins
* [ ] First Game Mode
* [ ] Stress Test 5000 Users
* [ ] How to play video
* [ ] Basic Website

## Stage 1 - Open Beta

> Q1 2026

All Discord members are invited to join the game. During Stage 1 the team will be analysing the game to ensure everything runs smoothly.

### Progress:

* [ ] Stress Test Open Beta

## Stage 2 - Open Public Beta

> Q1 2026

Everyone is invited to join the game. During Stage 2 we will focus in improving the website and finish the Tailer Video.

### Progress:

* [ ] Stress Test Open Public Beta
* [ ] Trailer Video
* [ ] Certification

## Stage 3 - Launch

> Q2 2026

The following timeline outlines the order in which deposit, and withdrawing will become available in the game.

### Progress:

* [ ] Smart Contract
* [ ] PinkSale Fair Launch.
* [ ] Enable Deposit and Withdraw in BSC mainnet

## Stage 4 - Upgrade

> Q3 2026

The following timeline outlines the implementation of new features after launch

### Progress:

* [ ] Merge Towers
* [ ] Weekly Box Lottery
* [ ] Remake Website
* [ ] Level 4 Tower NFT
* [ ] Hall of Fame Weekly Reward


---

# 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://whitepaper.cryptotd.me/fundamentals/roadmap.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.