Hyperliquid · quantitative infrastructure

Non-custodial execution
on Hyperliquid.

TrustAlgo is a boutique quantitative execution firm. We run non-custodial, latency-optimized models on a single venue: Hyperliquid. Capacity is strictly capped to preserve alpha decay and minimize slippage.

View Architecture Request Node

STATUS: ENGINE ACTIVE | CAPACITY: LIMITED | VENUE: HYPERLIQUID

VENUEHyperliquid only

CUSTODYMaster wallet

SIGNERAPI wallet

ACCESSLimited

01 — INFRASTRUCTURE

Built for one book, not a venue router.

VENUE

Hyperliquid only

The stack is scoped to Hyperliquid. No multi-DEX routing, no second book, no fallback venue.

CUSTODY

Keys stay local

Non-custodial by design. Assets and signing remain with the operator. The proxy executes; it does not hold.

CAPACITY

Capped on purpose

Total execution capacity is limited. Fewer concurrent flows means less self-impact and slower alpha decay.

02 — SCOPE

What a node is. What it is not.

A node is an execution seat on your Hyperliquid account. TrustAlgo signs orders with the API wallet you authorize. Collateral and withdrawals stay on the master wallet.

YOU GET

The node

One execution seat, while intake is open
Order flow on the Hyperliquid book only
Size kept inside the capped capacity

YOURS

What stays with you

Master wallet and withdrawal rights
Collateral on Hyperliquid
Revocation of the API wallet, at any time

NEVER

What TrustAlgo cannot do

Withdraw or move collateral
Trade any venue other than Hyperliquid
Recover a private key you did not keep

03 — OPERATING MODEL

A software house for Hyperliquid execution.

The stack is the product: quantitative infrastructure for operators who need to trade Hyperliquid without handing over custody.

VENUE

Hyperliquid only. Perps and spot sit on its on-chain order book, not an AMM pool.

LATENCY

Models are tuned to the Hyperliquid book: timing, size and queue position, not cross-venue routing.

SLIPPAGE

Size is constrained so the model does not become its own market impact.

ACCESS

Engine is active. New nodes are admitted only while capacity remains.

04 — SETUP

Connect a wallet. Create an API wallet.

Hyperliquid does not issue a classic exchange API key. You connect the master wallet, fund the account, then authorize an API wallet. The API wallet can sign trades. It cannot withdraw.

Connect the master wallet

Open app.hyperliquid.xyz and connect MetaMask, Rabby, or WalletConnect. Sign the connection request. That signature identifies the account. It does not grant TrustAlgo, or the API wallet, withdrawal rights.

Deposit collateral

Use Deposit in the app and send USDC on a network the deposit window lists. The minimum credited deposit is 5 USDC. Amounts below that are not credited. Wait until the balance shows on Hyperliquid before creating the API wallet.

Open the API page

Go to More, then API, or open app.hyperliquid.xyz/API. An API wallet is an agent wallet: it signs for the master account. Info requests still use the master address, not the agent address.

Name it, then generate

Enter a name, for example trustalgo. Click Generate. A named wallet is easier to track. An account can keep one unnamed API wallet and up to three named ones. Approving a new wallet with the same name replaces the previous one.

Copy the private key, then authorize

The dialog shows the private key once. Copy it into a password manager before you authorize. Then click Authorize API Wallet and sign with the master wallet. Default validity is 90 days. The maximum is 180 days. Hyperliquid will not show the key again.

Hand the key only to the node

Keep the master address and the API wallet private key separate. The master address is the account. The private key is the signer. Do not paste either into this page. Request a node, then deliver the key through the channel TrustAlgo gives you. You can revoke the API wallet on the same API page at any time.

Scope. The API wallet can place and manage orders. It cannot withdraw. Withdrawals stay on the master wallet. If the key is lost, generate a new API wallet. Do not reuse a deregistered agent address.

05 — ACCESS

Intake is limited.

Request a node. Seats are capped so the execution model stays inside its design envelope. There is no queue.

Request Node