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

# Phases

**Alpha** **- Incentivized Testnet** \
The smart contracts that make up the distributed game will first be tested on a testnet.

**Phase 1 - Jockey mint and stables mint, race-to-earn dynamic**\
We will kick-off the game by minting jockeys, which in turn allow for minting stables and horses by owning them. In this race-to-earn period, races can be done to earn STABLE coin from the centralized racetrack.

**Phase 2 - Jockey rental system activated**\
During this phase, the jockey renting interface will be deployed and users will be able to borrow and lend out jockeys on the marketplace. This allows jockey owners to earn STABLE coins by renting them out, and non-owners can rent it to play races and train their horses.

**Phase 3 - Race-to-earn inflationary era finished, betting mode activated**\
When all STABLE coins have been released, the inflationary epoch ends and users can no longer earn STABLE through races. The betting interface is deployed and all races will be about betting as opposed to earning through racing!

**Phase 4 - Racetrack minting**\
In this phase, users with a jockey can choose to freeze their jockey into a racetrack. This way, the user won't be able to use the jockey anymore but can instead allow other users to use the racetrack and earn a fee!

**Phase 5 - 3D gameplay launch**\
To make the game a truly immersive experience, Stable Empires will become a real 3D game for web3. Users will be able to see their races in a 3D interface, play like characters and operate in a metaverse-like world.


---

# 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://stableempires.gitbook.io/stable-empires-litepaper/roadmap/phases.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.