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

# Road Map

**▶︎  Stage 1:** 

* Group Formation
* Orbeon Protocol website creation
* Website launch
* Build social communities
* Smart contract development 
* Orbeon Protocol token audit 
* Phase 1 marketing campaign 
* Launch public presale 

**▶︎  Stage 2:**

* Complete all 12 phases of presale
* Presale token burn
* Launch on Uniswap
* Launch OrbeonSwap
* Coin Market Cap Listing
* Coingecko Listing
* Phase 2 marketing campaign
* Beta development of marketplace
* IOS & Android development
* Phase 2 marketing campaign

**▶︎  Stage 3:** 

* Launch on CEX
* Accepting applications for launchpad projects
* Governance smart contract development
* Orbeon launchpad release (Beta)
* Round table NFT launch
* Orbeon exchange launch
* Private Investor club launch

**▶︎  Stage 4:**

* Orbeon Wallet Development
* Multi-chain integration
* Tier-1 CEX listing
* Onboard brand ambassador

**▶︎  Stage 5:**

* Metaverse Launch (Orbiverse)
* Become a crypto unicorn 


---

# 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://orbeonprotocol.gitbook.io/orbeon-protocol/road-map.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.