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

# HyperCore

***Note:** The information in this page is based on the* [*official Hyperliquid L1 documentation*](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-l1)*. The **source code** of the L1 is **not yet publicly available**, so all details here are subject to change as the project evolves.*

***

Hyperliquid is purpose-built to meet the rigorous demands of an on-chain derivatives exchange. Its architecture enables decentralized trading with unprecedented speed and throughput, setting it apart from more generalized blockchain solutions.

#### System Overview

Below is a diagram illustrating the general functionality of HyperCore (=Hyperliquid L1), showcasing its key components and how they interact to deliver high-performance, scalable trading infrastructure:

<figure><img src="/files/YMSPCxzaS2F3oHLAVULC" alt=""><figcaption></figcaption></figure>


---

# 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://hyperliquid-co.gitbook.io/wiki/architecture/hypercore.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.