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

# Roadmap

{% hint style="info" %}
**This section is under development and may change over time.**
{% endhint %}

## Building the Future of Decentralised Value-Based Questing

### Phase 1

* [x] Launch ARKADA Website
* [x] Launch ARKADA Dapp
* [x] Launch Chapter 1: Shogun
* [x] Initiate Community Growth & Engagement Campaign
* [x] Launch User Profile

### Phase 2

* [x] Launch ARKADA Referral System
* [x] Launch Quest Leaderboard
* [x] Launch ARKADA Score (BETA)
* [x] Launch First ASTR-Incentivized Campaigns

### Phase 3

* [x] Launch ranking system (BETA)
* [x] Launch First Premium Quests (BETA)
* [x] Launch Trophy Hall
* [x] Integrate Multi-Chain Support
* [x] Improve ARKADA Score
* [x] Improve Ranking System
* [x] Improve User Profile 

### Phase 4

* [x] Launch Advanced Scoring Engine
* [x] Launch Performance HUB
* [ ] Update Questing Platform (ARKADA 2.0)

### Phase 5

* [ ] Launch ARKADA Quest Launcher (BETA)
* [ ] Launch White-label Suite (BETA)
* [ ] Improve Advanced Scoring Engine
* [ ] Over 2 Million Quest Participations

### Phase 6

* [ ] Launch ARKADA Staking Program
* [ ] TGE
* [ ] CEX & DEX Listings
* [ ] Launch Season 2

### Phase 7

* [ ] Non-EVM Chain Expansion
* [ ] Improve ARKADA Quest Launcher
* [ ] Improve White-label Suite

### Phase 8

* [ ] Launch ARKADA Governance Model (Community Voting for Features)
* [ ] Launch ARKADA Mini App
* [ ] White-label Suite Expansion To WEB2


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.arkada.gg/roadmap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.