# TECHNICAL ARCHITECTURE

Harmonix is infrastructure on Hyperliquid’s L1, using HyperBFT for consensus, HyperEVM for execution, and connected to HyperCore. Users benefit from earning native **HyperBFT Yield** (Perps, Lending, Borrowing, Staking, etc.) as well as tokens from the HyperEVM ecosystem as a reward for early contributions to the protocol.

1. **Hyper BFT:** Is the consensus layer where transactions are validated, keeping Hypercore and HyperEVM fast and synchronised.
2. **HyperCore:** Is the execution layer where the Hyperliquid protocol is built, so Perps, Staking, spot and HLP are here.
3. **HyperEVM:** Is the execution layer where **Harmonix is built**, also housing additional protocols like Felix, Hyperswap, Kentetiq and more.

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


---

# Agent Instructions: 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:

```
GET https://harmonix-finance.gitbook.io/harmonix-docs/technical-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.