> 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.md).

# Upshift HyperCore Relayer

The Hypercore Relayer is a long-running service that lets users deposit into a HyperEVM tokenized vault directly from HyperCore. A user's funds first arrive in the relayer's account on HyperCore (Hyperliquid's L1 ledger). The relayer detects that arrival in real time, bridges the funds from HyperCore to HyperEVM, and then deposits them into the destination tokenized vault on the user's behalf.

The service runs as one process per vault. HyENA Liquidity Provider Vault (HLPe) is supported by the Upshift Hypercore Relayer service. You can use it [here](https://app.hyena.trade/hyena/vault).

<table data-header-hidden><thead><tr><th width="257.05078125"></th><th></th></tr></thead><tbody><tr><td>Term</td><td>Meaning</td></tr><tr><td>HyperCore</td><td>Hyperliquid's native ledger where token balances and transfers live. Incoming user funds land here first, in the relayer's account.</td></tr><tr><td>HyperEVM</td><td>The EVM-compatible chain where the tokenized vault lives. Deposits are ultimately made here.</td></tr><tr><td>Bridge</td><td>The HyperCore to HyperEVM transfer of the relayer's own balance. This moves value across the two environments before the vault deposit can happen.</td></tr><tr><td>Tokenized vault</td><td>The destination on HyperEVM. Users receive vault shares for their deposit.</td></tr><tr><td>Relayer address / vault</td><td>The address the service watches and acts on behalf of. Signing is done through a MPC EOA wallet (Fordefi), so the service never holds raw private keys.</td></tr><tr><td>Transfer hash</td><td>The unique identifier for a single user deposit, used as the primary key throughout the pipeline and in the database.</td></tr><tr><td>Non-funding ledger update</td><td>A Hyperliquid websocket event type representing balance changes other than funding payments. Incoming deposits surface here.</td></tr></tbody></table>


---

# 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.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.