Tradable tokens
Why a spot buy needs the token enabled first, and how the open universe works
NAV counts a spot token only if the vault has enabled it. That single rule is what keeps a vault's accounting honest: nothing un-enabled can inflate NAV, and a buy of an enabled token is counted from the very first fill — no NAV dip while accounting catches up.
The open universe
There is no protocol-curated allowlist for spot. Any live, USDC-quoted Hyperliquid spot token is enable-able — the vault validates the token on-chain when you enable it, so the universe is exactly what Hyperliquid lists, nothing narrower.
(This is separate from HIP-3 builder-dex perps, which are a protocol-curated set — see trading. Curation applies to those synthetic perp venues, not to spot.)
Enabling a token
- Find it — search by symbol on Manage → Holdings → Tradable
tokens, or start a spot buy on
/tradeand the ticket prompts you inline. - Enable it — a one-time, wallet-signed on-chain transaction (⛓). This adds the token to the vault's counted set, so NAV values it from the first fill.
- Trade it freely through the agent (⚡) afterwards. Enabling is once per token, not per trade.
Selling is never gated — a sell only ever acquires USDC, so you can always exit a position whether or not the token is still enabled.
Bounded and prunable
Enabling is manager-only and the counted set is bounded (a fixed number of slots), so the accounting surface stays small and auditable. A token the vault no longer holds can be pruned to free its slot; pruning one the vault still holds is blocked, so a live position can never fall out of NAV.
In the cockpit: Manage → Holdings → Tradable tokens lists what's enabled, the slot count, and the enable / prune controls.