# Sovrun Nexus

### Sovrun Nexus: The Engagement Layer

The Engagement Layer focuses on delivering engaging, consumer-facing experiences that are accessible to a broad audience, this layer is dedicated to building user-friendly applications and experiences that will introduce and onboard new users and making decentralized gaming both approachable and compelling.

### GIG

**Questing Platform that Turns Mobile Telecom Operators into Channel Partners and Subscribers Into Engaged Users, Scaling Acquisition with Ease**

[GIG](http://home.gigrewards.ph) is a dynamic questing and rewards platform revolutionizing user engagement, bringing Web3 projects to Web2 users by turning mobile telecom operators into channel partners for user acquisition and engagement at scale. Telecom mobile subscribers can do quests, tasks, and missions to earn rewards. Quests can be gaming, shopping, referrals, social media participation, and other micro tasks that drive engagement and revenue. GIG's first partner is the largest telecom operator in the Philippines with access to over 60M subscribers, empowering users to earn while they engage.

[Visit GIG](http://home.gigrewards.ph)

### Chain Tactics

A fully on-chain 1v1 PvP strategy game where players command units on a 9x9 grid, blending chess-like strategy with RPG elements to outmaneuver opponents. Built using the Sovrun SDK, it showcases scalable, decentralized gameplay **(see \[Sovrun SDK]\(#sovrun-sdk) for details)**.

Learn more about [Chain Tactics](/build-with-sovrun/chain-tactics.md)

<br>

\ <br>


---

# 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/sovrun-nexus.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.