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

# Roadmap

### **Q1 / 2021**

<mark style="color:green;">1.Game Concept ✔</mark>

<mark style="color:green;">2.Team Setup ✔</mark>

<mark style="color:green;">3.Game Design ✔</mark>

* <mark style="color:green;">Gameplay design</mark>
* <mark style="color:green;">NFT metadata design</mark>
* <mark style="color:green;">Economy design</mark>

<mark style="color:green;">4.Initial Prototype ✔</mark>

* <mark style="color:green;">Android/ iOS prototype diagram and requirements document</mark>
* <mark style="color:green;">Web prototype and requirements document</mark>
* <mark style="color:green;">Game art prototype and requirements document</mark>

### Q2 / 2021

<mark style="color:green;">1.R\&D ✔</mark>

* <mark style="color:green;">Web development</mark>
* <mark style="color:green;">Smart contract development</mark>
* <mark style="color:green;">Android/ iOS development</mark>
* <mark style="color:green;">Art Design</mark>

<mark style="color:green;">2.Pirave sale ✔</mark>

### **Q3 / 2021**

<mark style="color:green;">1.Dragonmaster V1.0 Alpha test ✔</mark>

* <mark style="color:green;">Web Alpha test</mark>
* <mark style="color:green;">Smart Contract Alpha test</mark>
* <mark style="color:green;">Android/ iOS) Alpha test</mark>
* <mark style="color:green;">Original soundtrack</mark>

### **Q4 / 2021**

<mark style="color:green;">1.Whitepaper release ✔</mark>

<mark style="color:green;">2.NFT Public Pre-sale ✔</mark>

<mark style="color:green;">3.Public Beta test 1.0: only for Pre-sale players and community members ✔</mark>

* <mark style="color:green;">Web</mark>
* <mark style="color:green;">Android</mark>
* <mark style="color:green;">Original soundtrack</mark>

<mark style="color:green;">4.Collect feedback and suggestions from community members ✔</mark>

### **Q1 / 2022**

<mark style="color:green;">1.Smart contract audit ✔</mark>

<mark style="color:green;">2.Public Beta test 2.0 ✔</mark>

* <mark style="color:green;">Web</mark>
* <mark style="color:green;">Android / iOS</mark>

<mark style="color:green;">3.Token Public Sale ✔</mark>

<mark style="color:green;">4.Official launch ✔</mark>

* <mark style="color:green;">Web</mark>
* <mark style="color:green;">Android/ iOS</mark>

<mark style="color:green;">5.Profit sharing ✔</mark>

<mark style="color:green;">6.DMT Tournaments ✔</mark>

### **Q2 / 2022**

1.Ring Match

2.Multiplayer Match

3.Decentralized NFTs Rental Market

4.TOTEM Tournaments

### **Q3 / 2022**

1.Offline regional tournaments

2.Online tournaments (Streaming)

3.SocialFi exploration: We want to help players earn more by financializing DragonMaster's social influence

### **Q4 / 2022**

1.DMT Staking

2.Land auction

### **2023**

1.Land game: players start from 0 and build their own kingdom.&#x20;

2.DAO governance&#x20;

3.Developer Platform&#x20;

4.DragonMaster SDK: enables game developers to create games that use DragonMaster assets and operate them on their own decentralized network.


---

# 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://whitepaper.dragonmaster.co/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.