> For the complete documentation index, see [llms.txt](https://hellstreet.gitbook.io/hellstreet-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hellstreet.gitbook.io/hellstreet-docs/info/game-engine/partners.md).

# 👨‍🚀 Partners

{% hint style="info" %}
HellStreet’s partner ecosystem is built around the tools, services, and people that make the platform functional, scalable, and believable as a real digital world. The partner layer includes infrastructure providers, blockchain services, payment integrations, engine technology, and selected private individuals who contribute expertise in product strategy, growth, creative direction, and community development. This mix is important because a platform like HellStreet depends on both technical reliability and human judgment.
{% endhint %}

#### Partners

| Company / Person  | Date       | Type                                            |
| ----------------- | ---------- | ----------------------------------------------- |
| **Unreal Engine** | 22.08.2022 | Licensing Agreement + NDA                       |
| **Chainlink**     | 05.02.2023 | Service Agreement + NDA + SLA                   |
| **Transak**       | 18.04.2023 | API Integration Agreement + NDA                 |
| **Covalent**      | 12.07.2023 | API Integration Agreement + Licensing Agreement |
| **Sequence**      | 29.09.2023 | API Integration Agreement + NDA                 |
| **Elena Voss**    | 14.01.2024 | Strategic Advisory + Collaboration Agreement    |
| **Daniel Rhee**   | 02.03.2024 | Community Partnership + Consulting Agreement    |

#### Partner Information

{% tabs %}
{% tab title="1. Unreal Engine" %}
Unreal Engine is a natural technical partner for a project like HellStreet because it provides the real-time 3D foundation needed for a high-fidelity urban world. Its rendering capabilities, animation systems, and scalability make it suitable for immersive environments, social hubs, and event-driven spaces. For HellStreet, this partnership supports the visual quality and performance expectations that players now associate with modern interactive worlds.
{% endtab %}

{% tab title="2. Chainlink" %}
Chainlink is important as a blockchain infrastructure partner because it helps connect on-chain systems with external data, automation, and verifiable logic. In a platform that uses ownership, tokenized assets, and marketplace activity, reliable oracle infrastructure matters a lot. It adds trust to systems that may depend on price feeds, event triggers, reward logic, or transparent verification processes.
{% endtab %}

{% tab title="3. Transak" %}
Transak fits naturally into HellStreet’s ecosystem as a payment and onboarding partner. Projects with digital ownership and creator-driven economies often need a smoother path between traditional payment flows and blockchain-native interactions. A service like this can reduce friction for users who want to buy access, purchase assets, or move into Web3 without a complicated setup process.
{% endtab %}

{% tab title="4. Covalent" %}
Covalent is useful for data access, indexing, and multi-chain visibility. For HellStreet, that means better support for asset discovery, ownership tracking, analytics, and ecosystem transparency. When a platform spans worlds, marketplace activity, and tokenized items, clear data infrastructure becomes essential for both internal operations and user-facing tools.
{% endtab %}
{% endtabs %}

{% tabs %}
{% tab title="5. Sequence" %}
Sequence provides a strong account and wallet layer for applications that want a more seamless user experience around digital ownership. In HellStreet, that kind of partner is valuable because the project benefits from reducing wallet friction while still preserving the benefits of ownership, transferability, and in-world commerce. It helps the platform feel more accessible to non-technical users.
{% endtab %}

{% tab title="6. Elena Voss" %}
Elena Voss is an independent strategic advisor focused on product presentation, creator ecosystem design, and community-first growth. Her role is to help refine how HellStreet communicates its value, how creator programs are structured, and how showcase content is positioned for audience engagement. Private advisors like this can be especially useful when the project is building its public identity and needs a sharper narrative.
{% endtab %}

{% tab title="7. Daniel Rhee" %}
Daniel Rhee works as a community partnership consultant with experience in digital events, collaborative campaigns, and ecosystem outreach. His contribution is less about infrastructure and more about how the platform grows socially — how creators are activated, how partnerships are introduced, and how the project stays visible without losing its core identity. This type of relationship is valuable for a living platform where community energy matters as much as technology.
{% endtab %}
{% endtabs %}


---

# 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://hellstreet.gitbook.io/hellstreet-docs/info/game-engine/partners.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.
