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

# The Solnarize Ecosystem

**Concept**: "Solar Defender" is an innovative blockchain-based game where players protect a solar-powered city from environmental hazards. The goal is to maintain the city's solar energy supply by strategically placing and upgrading solar panels while defending against challenges. Players stake their $SRIZE tokens to play the game, and successful gameplay rewards them with additional $SRIZE tokens.

**Gameplay**:

* **Objective**: Protect a city powered by solar energy. Players must strategically place and upgrade solar panels while defending them from obstacles like dark clouds, pollution, and other environmental threats.
* **Controls**: Point-and-click or tap controls to place solar panels, deploy defenses, and upgrade installations.
* **Levels**: Different levels represent various parts of the city, each introducing new challenges and requiring more sophisticated strategies.
* **Defenses**: Deploy defenses such as wind turbines to blow away clouds, water purifiers to clean polluted areas, and energy shields to protect solar panels.
* **Rewards**: Players earn points by keeping the city's energy levels high. Points are converted into $SRIZE tokens, which are airdropped to their wallets after each level.
* **Challenges**: Randomized environmental events like storms, pollution waves, and nighttime phases to keep gameplay dynamic and challenging.


---

# 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://docs.solnarize.com/introducing-solnarize/the-solnarize-ecosystem.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.