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

# 7. Roadmap to Mainnet

* **Phase 1: Bootstrapping (Current Phase)**
  * Launch of Lava Chrome Extension and Desktop App.
  * Point farming and Proof of Uptime tracking goes live.
  * Strategic B2B partnerships established for enterprise bandwidth utilization.
* **Phase 2: The Testnet Era**
  * Introduction of the Lava Blockchain Testnet.
  * Active nodes transition to processing live testnet transaction routing.
  * Global leaderboard expansion and stress testing.
* **Phase 3: Mainnet Launch & TGE**
  * The Token Generation Event (TGE).
  * Airdrop distribution to early node operators based on accumulated points.
  * Transition from centralized tracking to fully on-chain rewards.
* **Phase 4: Ecosystem Scaling**
  * Launch of Mac and Linux clients.
  * Open API for developers to easily integrate Lava RPCs into their dApps.


---

# 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://lava-network.gitbook.io/lava-network-docs/7.-roadmap-to-mainnet.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.