> For the complete documentation index, see [llms.txt](https://docs.upshift.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.upshift.finance/vault-architecture/upshift-hypercore-relayer/high-level-architecture.md).

# High-Level Architecture

The service is a pipeline of four asyncio components connected by three bounded queues. A single user deposit flows left to right through them:

1. **Reader**: keeps a websocket open to Hyperliquid, subscribes to the relayer's non-funding ledger updates, and pushes raw matching messages onto message\_queue. It never does heavy work itself, so the receive loop never blocks.
2. **Message dispatcher**: pulls messages off message\_queue and spawns a processing task per message, bounded by a semaphore. Detected deposits are enqueued onto bridge\_queue.
3. **Bridge worker**: pulls a batch off bridge\_queue, bridges the aggregate amount from HyperCore to HyperEVM, marks the transfers as bridged, and forwards each transfer to deposit\_queue.
4. **Deposit worker**: pulls a batch off deposit\_queue and submits a single on-chain batchDeposit call to the vault via the Fordefi-signed BatchDepositor.


---

# 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.upshift.finance/vault-architecture/upshift-hypercore-relayer/high-level-architecture.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.