Vault Architecture
HyperCore Relayer
A long-running service that detects deposits arriving on HyperCore, bridges them to HyperEVM, and deposits them into a tokenized vault on the user's behalf.
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 at app.hyena.trade/hyena/vault.
Terminology
| Term | Meaning |
|---|---|
| HyperCore | Hyperliquid's native ledger where token balances and transfers live. Incoming user funds land here first, in the relayer's account. |
| HyperEVM | The EVM-compatible chain where the tokenized vault lives. Deposits are ultimately made here. |
| Bridge | The HyperCore to HyperEVM transfer of the relayer's own balance. This moves value across the two environments before the vault deposit can happen. |
| Tokenized vault | The destination on HyperEVM. Users receive vault shares for their deposit. |
| Relayer address / vault | 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. |
| Transfer hash | The unique identifier for a single user deposit, used as the primary key throughout the pipeline and in the database. |
| Non-funding ledger update | A Hyperliquid websocket event type representing balance changes other than funding payments. Incoming deposits surface here. |