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

# Roadmap

Step 1

* Market research
* Team establishment
* Web 3 core smart contract’s development phase started

Step 2

* Creating documentation 
* Creating the marketing strategy 
* Beta launch of sport events functionality 
* PolyFarm bot development phase

Step 3

* NFT collection sale  
* Public launch of sport events functionality 
* Prediction platform development phase 
* Public token sale
* Web 3 games, lottery development phase
* Web 3 casino developments phase

Step 4

* White Label: web 3 sport betting platform 
* Marketing, influence campaigns
* Beta launch of the web 3 games 
* Beta launch of the web 3 lottery  
* $PLW DEX listing

Step 5

* $PLW Tier-1 CEX listing 
* Airdrop and bounty activities
* Beta launch Web3 casino 
* White Label: web3 blockchain casino  

Step 6

* Beta launch Polyway.io prediction platform 
* New update roadmap 


---

# 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://polyway.gitbook.io/polyway/ecosystem-overview/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.