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

# Roadmap

<details>

<summary>2023 Q4</summary>

* Square Enix & Solana Foundation led seed round.&#x20;
* Elixir acquires LitLab Games.
* Publishing of Overlay technology powering +130 games by $ELIX.

</details>

<details>

<summary>2024 Q1</summary>

* NFT Freemint.
* $ELIX TGE & CEX listing.
* Launchpad.
* Season pass.
* State-of-the-Art Airdrop Tech for games.

</details>

<details>

<summary>2024 Q2</summary>

* Invisible wallets (Account Abstraction).
* On-Ramp payments.
* $ELIX cashback system.
* $ELIX nodes.

</details>

<details>

<summary>2024 Q3</summary>

* Minting tools.
* Mobile app.
* LayerZero Bridge.
* Swap Aggregator.

</details>

<details>

<summary>2024 Q4</summary>

* NFT Marketplace.
* Fiat-enabled Launchpad.
* $ELIX Visa.
* Elixir Game Awards.

</details>

<details>

<summary>2025 Q1</summary>

* 10 incubated projects have an IDO on Elixir Launchpad.
* +200 listed games.
* $ELIX hardware wallet limited edition.
* AI-powered launcher that enables GPU rental for $ELIX tokens.

</details>


---

# 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://whitepaper.elixir.games/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.