> 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/architecture-and-core-concepts.md).

# Architecture & Core Concepts

### High-level System Architecture <a href="#high-level-system-architecture" id="high-level-system-architecture"></a>

The Hyperliquid Stablecoin Dashboard is built on a modular and scalable architecture combining several state-of-the-art Web3 data indexing and user authentication technologies:

* **Goldsky Pipelines**: Stream on-chain token transfer data for multiple stablecoins directly into a PostgreSQL database. This ensures real-time data availability with low latency and high throughput.
* **PostgreSQL (Dockerized)**: Serves as the core data warehouse storing indexed blockchain data, providing flexible SQL querying capabilities.
* **Subgraphs**: Deployed alongside pipelines for GraphQL-based querying of specific or structured blockchain data, enabling developer-friendly API access.
* **Privy Authentication**: Offers a secure, multi-method login system with embedded wallets that do not require users to use external wallets.
* **Hyperliquid Names (.hl)**: Enhances user identity by displaying the user’s human-readable registered names associated with wallet addresses.

### Pipelines vs. Subgraphs: Strengths and Trade-offs <a href="#pipelines-vs-subgraphs-strengths-and-trade-offs" id="pipelines-vs-subgraphs-strengths-and-trade-offs"></a>

| Aspect         | Goldsky Pipelines                              | Subgraphs                                     |
| -------------- | ---------------------------------------------- | --------------------------------------------- |
| Data Latency   | Streaming real-time data, very low             | Query-based, moderate latency                 |
| Scalability    | High throughput, scalable for big data         | Suited for low to moderate traffic            |
| Query Language | SQL (powerful and flexible)                    | GraphQL (easy to use for developers)          |
| Query Limits   | No practical query size limits                 | Paginate queries to get all transaction data. |
| Data Model     | Flexible, combines on-chain and off-chain data | Structured primarily for on-chain data        |
| Infrastructure | User-managed storage & querying                | Hosted managed indexing service               |

### Key Components <a href="#key-components" id="key-components"></a>

* **Embedded Wallets**: Wallets created seamlessly within the app post-login, providing smooth UX by removing the need for external wallet extensions or apps.
* **Real-time Whale Alerts**: Pipeline data triggers customizable alerts notifying users of significant token transfers.
* **Identity Integration**: Wallet addresses linked to Hyperliquid Names (.hl) provide human-friendly identity display that improves usability.
* **Notification Channels**: Alerts can be delivered via Telegram, Discord, or other platforms (planned for future development). Only telegram implemented for now.


---

# 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/architecture-and-core-concepts.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.