# About Sovrun

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXePyyb3pIugbP-HulbybGm5prkZT-KoAR_XJfrerqweHJYgw3wzwDXU6ZqMQuCsgA9m8DemUB287J4mT_5dbVXLt5jsO1OFaxCxskxfUE-uKCzENbDIXRW9_KjP1t2bLgnAOVXaTw?key=weo2vl887S6ZT9ibnwfRY5gJ" alt=""><figcaption></figcaption></figure>

### Genesis

The Participation Layer unites human and financial capital, enabling players, creators, and communities to shape game economies. Sovrun Genesis fosters trend identification, project contributions, and impactful decision-making, cultivating true ownership in digital worlds. Leveraging years of Web3 gaming expertise, it positions Sovrun as a leader in on-chain participation.

### Labs

Sovrun Labs drives innovation in game development with tools designed for simplicity and scalability:

* **Headless Clients:** Allow developers to build and mod applications without managing blockchain complexity directly.
* **Account Abstraction:** Simplifies user onboarding and interactions, removing technical barriers.
* **Ultra-low Latency:** Delivers fast, responsive gameplay essential for real-time experiences.

These advancements empower developers to create flexible, community-driven games.

### Nexus

Sovrun Nexus is the engagement layer, offering user-friendly platforms to bring decentralized gaming to a wider audience:

* **GIG:** A questing platform partnering with telecom operators to boost user acquisition.
* **Chain Tactics:** A fully open source onchain strategy game where players command units to outsmart opponents on a 9x9 grid. Developers can get from 0 to 1 on any EVM or L2, using this game template, MUD Framework, smart contracts and Unity client.


---

# Agent Instructions: 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:

```
GET https://docs.sovrun.org/intro-to-sovrun/about-sovrun.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.