> For the complete documentation index, see [llms.txt](https://shodo-veil.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shodo-veil.gitbook.io/whitepaper/the-founding-team/about-us.md).

# About Us

Anything on this page is subject to change throughout the development progress of the game. We will thoroughly test and validate any feature before it goes live.

SV Studio was born in 2025 with the vision of creating new gaming experiences based on the new possibilities that blockchain and crypto technologies were bringing to the industry. and since then the team has been able to onboard over 70 full-time staff across various roles, including Product Owners, Game Designers, Economists, Blockchain Developers, Unity Developers, HR, Customer Support, User Acquisition and more. This growth reflects the dynamic and diverse nature of SV's endeavors.

We are looking for great partners and sponsors to be part of our growth, accelerate working progression, and scale up our community.


---

# 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://shodo-veil.gitbook.io/whitepaper/the-founding-team/about-us.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.