Hyperliquid setup
Current availability: Add account → Hyperliquid is a visual setup preview. It does not request a wallet connection, accept a private key, approve an agent or enable trading. Multi-venue execution is disabled.
Prerequisites
Sign in to VertigoPro to access Add account. No funded account or key is needed to inspect the preview. Existing Hyperliquid users should retain access to their main wallet and the venue’s own application for account management.
Create and fund a Hyperliquid account
Account creation and deposits take place at Hyperliquid, outside VertigoPro. Follow the venue’s current deposit instructions and verify the network and destination there before transferring funds. Funding is not necessary for this preview and will not enable execution in VertigoPro.
Choose a connection method
- Select Add account, then Hyperliquid.
- Choose Browser wallet, WalletConnect or API key.
- Inspect Select account or API details, then select Continue.
- Review the exchange, account name and method under Authorize.
- Select Preview connection. Complete or skip the optional layout and theme previews.
The resulting account entry is marked Preview. The example account choices do not represent accounts discovered from your wallet. Layout and theme selections in this flow are temporary; use the actual workspace and appearance settings to save changes.
Browser wallet
Selecting this method advances the preview immediately. It does not open Rabby, MetaMask or another wallet and does not prove control of an address.
WalletConnect
The preview does not establish a WalletConnect session or produce a connection request to approve on your phone.
Existing API wallet
The interface calls this option API key. Account address and API wallet private key are read-only fields marked Preview only. There is no current import procedure through this flow.
Confirm wallet ownership
The current preview performs no ownership verification. In the existing Hyperliquid authorisation implementation, an ownership message binds the connected main wallet to the VertigoPro profile. That is separate from wallet-based registration.
Review API-wallet permissions
A Hyperliquid API wallet is a signer authorised by the main wallet. Account queries must use the main or subaccount address, not the API-wallet address; querying the signer can return an empty account. This distinction comes from Hyperliquid’s API-wallet model.
The preview label Approve API wallet does not perform that approval. Security covers the existing signing and storage boundaries.
Approve the builder fee
No fee approval occurs in the preview. The existing integration specifies a maximum approval of 0.01% (1 bp). A real builder-fee approval is a separate main-wallet signature; it is not an order or a deposit. The fee reference explains where this fee applies.
Confirm trading readiness
A Preview entry is not a ready trading account. A live price, account balance or unlocked legacy agent also does not override the current multi-venue execution restriction. A disabled order control stating Execution will be enabled after this multi-venue review is an availability boundary, not a funding error.
Switch subaccounts
Main account and Subaccount 1 in the preview are examples. Selecting either does not select a real venue subaccount. For public account inspection, use the separate account scope and spectating controls and verify the address.
Disconnect or revoke an API wallet
Removing a preview account only removes its temporary entry. Forgetting a saved descriptor or signing out does not revoke a Hyperliquid approval. Review actual agents through Hyperliquid’s API-wallet page when withdrawing venue access.
Before revoking an agent used elsewhere, check which other sessions rely on it. Revocation is not an order-cancellation procedure: inspect outstanding orders and positions at the venue separately.
Agent-limit and recovery errors
Existing Hyperliquid agent recovery can report a device-agent limit, an unconfirmed approval or an unlock failure. VertigoPro’s existing registration guard allows three active agents per Hyperliquid account within a profile; this is not a statement of the venue’s total agent limit.
For an ambiguous approval, reconcile its venue status before creating another agent. For a lost device credential, retain access through the main wallet and revoke obsolete venue authorisations. Do not reuse a deregistered API-wallet key; Hyperliquid warns that its nonce history can be pruned. These recovery paths concern real existing agents, not preview entries.