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

# General FAQs

### General

<details>

<summary>What is Helix? </summary>

Helix is building a full-stack, omni-chain, stablecoin infrastructure layer for enabling issuance, distribution, diverse yield strategies, and seamless DeFi composability through a unified, modular architecture.

</details>

<details>

<summary>What is the Helix Orchestration Layer?</summary>

Helix orchestration layer provides a modular, full-stack, omni-chain infrastructure that supports the entire stablecoin lifecycle issuance, distribution, yield generation, interoperability, and TradFi-DeFi integration.

</details>

<details>

<summary>Who is it built for? </summary>

* Corporates, fintechs, and exchanges launching stablecoins
* Tokenisation platforms needing omni-chain and fintech grade RWAs
* Investment managers & neobanks offering yield products
* Ecosystems embedding stablecoins into payments/loyalty&#x20;

</details>

<details>

<summary>What sets Helix apart?</summary>

Helix combines modular, end-to-end infrastructure for institutions with a seamless DeFi-native experience for users. Unlike fragmented solutions, Helix offers:

* A full orchestration backend
* Omni-chain and fintech grade abstraction
* Customizable contracts and partners
* Multi-strategy yield access through Helix Hub

</details>

### Assets on Helix Hub

<details>

<summary>Can issuers use their own custodian/compliance providers?</summary>

Yes. Helix is a which can be use to built-in modules or integrate their own partners. The Pathfinding Engine (in progress) will help match issuers with optimal partners.

</details>

<details>

<summary>Can I launch across multiple chains?</summary>

Yes. Native omni-chain deployment is supported. This ensures seamless liquidity and contract deployment across EVM and non-EVM chains.

</details>

<details>

<summary>Is the Orchestration Layer decentralized?</summary>

Helix will provide a decentralized model powered by validators for issuance, enforcement, and cross-chain coordination. &#x20;

</details>

### Helix Hub and USHD

<details>

<summary>What is Helix Hub?</summary>

**Helix Hub** is a multi-strategy RWAFi platform built on the **Helix Orchestration Layer,** providing access to institutional-grade RWAs across the yield curve.&#x20;

</details>

<details>

<summary>What kind of assets will be are available on Helix Hub?</summary>

Helix will support high-quality RWAs such as:

* Money market instruments
* Private credit
* Structured credit products
* Other curated fixed-income portfolios

</details>

<details>

<summary>What is USHD?</summary>

USHD is a fully collateralized, dollar-pegged stablecoin backed by RWAs (money markets instruments)<mark style="color:yellow;">.</mark> It’s the foundational entry point of Helix Hub ecosystem.

</details>

<details>

<summary>How do I generate yield from USHD?</summary>

Stake USHD to mint USHDs, a reward-bearing token backed by tokenized money markets.

</details>

<details>

<summary>How is the collateral secured?</summary>

All USHD products are backed 1:1 by tokenized RWAs, held in segregated custody with regulated custodians, auditors, and proof-of-reserve systems.

</details>

{% hint style="warning" %}
Helix combines compliance-first design with DeFi-native infrastructure, ensuring adoption at scale without sacrificing security or regulation.
{% endhint %}


---

# 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.helixfi.io/faqs/general-faqs.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.