> 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/getting-started/helix-hub/helix-origin.md). # Helix Origin **Helix Origin** is the **inaugural testnet campaign** of Helix Hub, an omni-chain, community-first platform designed to make RWAFi accessible, engaging, and rewarding. ### Two Tracks of Engagement Helix Origin is built around two complementary tracks that introduce users to the Helix ecosystem through a gamified experience: 1. **Base Actions** > One-time tasks that provide users with an immediate introduction to Helix Ecosystem. 2. **Seasonal Actions** > Time-bound challenges that encourage continued engagement and exploration of the RWAFi world ### **Explore by Engaging** By completing actions such as: * Minting and staking USHD in a testnet environment * Participating in community events * Earning achievement badges Users not only learn how RWAFi works in practice but also gain lasting recognition and future perks within the Helix Ecosystem. --- # 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/getting-started/helix-hub/helix-origin.md?ask=&goal= ``` `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.