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

# Introduction

### Project Overview <a href="#project-overview" id="project-overview"></a>

The Hyperliquid Stablecoin Dashboard is a comprehensive tool designed to provide **real-time, scalable, and multi-token analytics** on the Hyperliquid stablecoins ecosystem. It combines streaming data pipelines powered by Goldsky with traditional subgraph querying, enabling fast, flexible, and enriched blockchain data insights.

### Motivation and Vision <a href="#motivation-and-vision" id="motivation-and-vision"></a>

Decentralized finance (DeFi) projects demand **low-latency, high-throughput data access** to support trading, analytics, and risk assessment workflows. Existing solutions often suffer from limitations like query result caps or high indexing latency.

Our vision is to build the **best stablecoin analytics dashboard in the HyperEVM ecosystem**, leveraging cutting-edge technologies such as Goldsky pipelines, PostgreSQL data warehousing, and embedded wallets with user-friendly authentication powered by Privy and Hyperliquid Names (.hl).

This project is designed to continuously evolve and empower developers, traders, and the broader Hyperliquid community with transparent, actionable on-chain insights.

### Target Audience <a href="#target-audience" id="target-audience"></a>

* DeFi Developers and Analysts seeking granular, real-time token transfer data.
* Traders and market makers focused on Hyperliquid stablecoins.
* Protocol designers in need of scalable, reliable data infrastructure.
* Community members wanting simple, seamless access through embedded wallets and personalized identity features.


---

# 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://hypernexus.gitbook.io/hyper-nexus/introduction.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.