Vault ArchitectureHyperCore Relayer
High-Level Architecture
The relayer is a pipeline of four asyncio components connected by three bounded queues.
The service is a pipeline of four asyncio components connected by three bounded queues. A single user deposit flows left to right through them:
- 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. - Message dispatcher: pulls messages off
message_queueand spawns a processing task per message, bounded by a semaphore. Detected deposits are enqueued ontobridge_queue. - 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 todeposit_queue. - Deposit worker: pulls a batch off
deposit_queueand submits a single on-chainbatchDepositcall to the vault via the Fordefi-signedBatchDepositor.
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.
End-to-End Flow
How a single deposit travels from arrival on HyperCore through bridging and batching to final vault settlement on HyperEVM.