> 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/3.-the-ecosystem-products.md).

# 3. The Ecosystem Products

To ensure maximum decentralization, we offer two distinct ways for users to participate in the network.

#### **A. Lava Chrome Extension (The Entry Level)**

* **Accessibility:** A lightweight browser extension designed for mass adoption.
* **Functionality:** Runs seamlessly in the background whenever the browser is open.
* **Reward Rate:** Base multiplier (1x). Perfect for casual users looking to step into the Web3 ecosystem.

#### **B. Lava Desktop App (The Power Node)**

* **Performance:** A robust Windows executable (.exe) designed for dedicated validators.
* **Functionality:** Operates independently of the browser, ensuring continuous network support even when the user is not actively surfing the web. It handles heavier data routing with optimized latency.
* **Reward Rate:** **5x Multiplier (Max Rewards).** Users running the Desktop App are the backbone of the Lava Network and are heavily incentivized with a 500% boost in $LAVA rewards compared to extension users.


---

# 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/3.-the-ecosystem-products.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.