# Roadmap

This page outlines Loadout’s planned development and key milestones.

### Phase 1: Launch (June 2026)

**Completed**

* Platform redesign and full branding uplift
* Multi-Game Studio Support (one studio token, multiple games)
* Match Gaming (Loot + XP rewards system)
* Referral Program with rebates
* First wave of curated studio launches (starting mid-June)
* Smart contract development and audits
* Bonding curve + Meteora DLMM integration
* Mainnet deployment
* Core trading mechanics
* Project submission system

### Phase 2: Growth (Mid to Late 2026)

* Advanced analytics and project dashboards
* Improved discovery, search, and filtering
* Enhanced mobile experience
* Treasury management tools and multi-sig support
* Expanded KOL and creator partnership program
* Community governance features (mvp)
* Performance optimizations and platform scaling

### Phase 3: Ecosystem Expansion (Late 2026 – 2027)

* Trade Syndicates (shared trading vaults)
* Staking module for the Loadout token
* In-platform game distribution and access features
* Advanced studio tools and analytics
* API access for third-party developers
* Cross-chain capabilities exploration

### Long-term Vision (2027+)

* Full game publishing and distribution layer
* On-platform game ownership and access passes
* Studio investment and revenue sharing tools
* Expanded multi-game and multi-studio capabilities
* DAO governance for key platform decisions

We are currently in the final stages before mainnet launch. The first studios are expected to go live in mid-June as part of the “30 Games in 30 Days” campaign.

This roadmap is living and will be updated regularly based on progress and community feedback.


---

# Agent Instructions: 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:

```
GET https://loadout.gitbook.io/product-docs/overview/roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.