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

# Orbit Roadmap

## 100% Community Focused

Orbit Marketplace is built by the community, for the community. For this reason, we want to gather as much community feedback and feature requests to improve our platform. We will start collecting feedback and feature requests once the platform is live on Evmos mainnet.

For now we have come up with a small roadmap for Orbit V1 & V2.

## Roadmap

### - April 2022

{% hint style="info" %}
Orbit mainnet deployment depends on Evmos mainnet launch itself. We expect Evmos mainnet to launch sometime in April 2022.
{% endhint %}

#### Deploy Orbit Marketplace V1

Orbit V1 features can be found [here](/orbit-marketplace/about.md#orbit-v1-marketplace-features)

### - Q3 2022

#### Deploy Orbit Marketplace V2

Orbit V2 features include:

* Auctions
* Browse collections by category
* Bundle buying/selling
* Configurable user profile
* Email notifications


---

# 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://docs.orbitalapes.com/orbit-marketplace/orbit-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.