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

# Roadmap

Where we are headed

## Roadmap

Roxin is being developed progressively.

The roadmap is based on proving useful value transfer before expanding the network.

### Phase 1 — Foundation

Current focus:

* ROXIN token infrastructure
* smart contracts
* public documentation
* project transparency
* ecosystem design
* developer research
* partner discovery

### Phase 2 — Controlled Pilot

Connect a small number of compatible games.

The pilot should demonstrate:

```
Game A
   ↓
Portable value
   ↓
ROXIN
   ↓
Game B
   ↓
Local utility
```

The goal is to measure actual player and developer value.

### Phase 3 — Developer Infrastructure

Turn the repeated integration work into reusable infrastructure.

Potential components include:

* SDKs
* APIs
* policy controls
* settlement records
* reporting
* reconciliation
* monitoring

### Phase 4 — Network Expansion

Add more games, value routes, partners, and player utility.

Growth should remain controlled so that participating developers retain authority over their economies.

### Long-Term Direction

Roxin aims to become infrastructure through which different games can recognize and transfer player value.

The goal is not one universal game economy.

The goal is a network of independent game economies that can communicate with each other.


---

# 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.roxin.network/project/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.