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

# Roadmap

<figure><img src="https://1918439769-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqBHFAzx3aZTo1p2Bz0qu%2Fuploads%2F0u8Xqf49I5qSxgfy7SgX%2Fphoto_2025-07-10_11-55-44%20(2).jpg?alt=media&amp;token=032fc791-5510-4d67-873a-ba2385d04ff2" alt=""><figcaption><p>Phases 1 - 4</p></figcaption></figure>

## ✅Phase 1: HYDRON - Lift Off

| 2025 Q2                                                                                                 |
| ------------------------------------------------------------------------------------------------------- |
| <ul><li>Public Roadmap Announcement</li><li>TGE Community Airdrop Criteria for $BMB Published</li></ul> |

## Phase 2: NEON - Signal &#x20;

| 2025 Q3                                                                                                                                                                                                                                                                                    |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <ul><li>Alpha Node Sale</li><li>Distribute Alpha Node License NFTs</li><li>Security Audits of Token Smart-Contracts </li><li>$BMB Token Pre-Sale Round</li><li>$BMB Community Airdrop Snapshot</li><li>Airdrop Platform Launch & Claim</li><li>Announce Workload Node Suppliers </li></ul> |

## Phase 3:  ARGON - Expansion

| 2025 Q4                                                                                                                                                                             |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Public Checker Node Sale</li><li>Distribute Checker Node License NFTs to Node Buyers</li><li>Checker Node Launch </li><li>Worker Node Liveliness Dashboard Launch</li></ul> |

## Phase 4:  KRYPTON - Infrastructure

| 2025 Q4                                                                                                                                                                                                                       |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>DAO Activated</li><li>Launch Orderbook V1 for Game Compute Workloads</li><li>Implement On-Chain payment settlement</li><li>Add Worker Completion Checks</li><li>Launch the Public Dashboard for the Project</li></ul> |

<figure><img src="https://1918439769-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqBHFAzx3aZTo1p2Bz0qu%2Fuploads%2FxM8N8jGk1StlZPkLuSGT%2Fphoto_2025-07-10_11-55-44.jpg?alt=media&amp;token=48bdade5-5294-423c-953e-8c0d8ac55f1a" alt=""><figcaption><p>Phases 5 - 7</p></figcaption></figure>

## Phase 5: XENON - Enforcement

| 2026 Q1                                                                                                                                                                                      |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Activate Slashing Mechanisms</li><li>Announce a Security Council for Governance</li><li>Activate Worker Node Reputation </li><li>Upgrade Orderbook to V2 Matching Criteria</li></ul> |

## Phase 6: OZONE - Scale & Migration

| 2026                                                                                                                                             |
| ------------------------------------------------------------------------------------------------------------------------------------------------ |
| <ul><li>Migrate Beamable Compute Workloads From Cloud Providers to Beamable Network </li><li>Upgrade Orderbook to V3 Matching Criteria</li></ul> |

## Phase 7: FUSION - Ecosystem

| 2026                                                                                                                                      |
| ----------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Launch Creator Ecosystem</li><li>Activate Creator Royalty Payments</li><li>Launch Partner Workload Migration Incentives</li></ul> |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.beamable.network/project-documentation/roadmap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
