Hyperliquid Spot Orderbook

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

REJECTED. The current Hyperliquid interface terms classify United States persons as Restricted Persons, which is a categorical bar for this US-advisor mandate. Spot trading also does not create protocol yield: the worklist TVL is inventory and balances held on HyperCore, with each token carrying issuer and market risk plus Hyperliquid validator, bridge, and order-book dependencies. Direct protocol calls or an alternate interface do not turn a restricted client into an eligible one.

Kill criteria: the events that revoke this verdict
• Hyperliquid publishes terms permitting this registry’s United States client population to use spot services
• The exact spot asset receives an approved asset-control profile and its issuer and transfer restrictions remain eligible
• A proposed-size native withdrawal completes through a documented bridge without an unreviewed third-party operator
• Any validator intervention that changes a spot settlement or any bridge loss opens an immediate review

The research file

Mechanism and client claim

HyperCore runs a native on-chain central limit order book. Users deposit supported assets, sign orders, and trade spot pairs represented by HIP-1 token deployments; HIP-2 can place protocol-native liquidity against selected USDC pairs. Balances and order execution live in Hyperliquid L1 state rather than an EVM smart contract, and some BTC, ETH, SOL and other deposits and withdrawals are handled by independent bridge teams such as Unit. Spot ownership is economically different from HLP or perpetual margin, but unified and portfolio-margin modes can let the same balance collateralize borrowing or derivatives if the user enables them.

Control, governance, and legal perimeter

The validator set orders and finalizes HyperCore transactions and signs native USDC bridge movements. The bridge credits deposits after more than two-thirds of stake signs and requires the same threshold for withdrawals; a dispute and cold-wallet unlock process handles challenged withdrawals. Token deployers choose asset metadata and may receive fees, while the interface operator controls access under its terms. Independent bridge teams can control non-USDC asset routes. The result is self-directed trading without a conventional broker, but not an absence of validators, issuer controls, bridge quorums, or legal eligibility.

Incident and operating record

Hyperliquid has a strong high-throughput operating record, but validator intervention during the March 2025 JELLY event and the previously reviewed HLP losses demonstrate that market and consensus controls can become active under stress. That event affected derivatives and HLP rather than proving a spot-custody loss, so this memo does not misattribute it. The spot-specific record instead includes evolving account modes, permissionless token deployment and independent asset bridges—features that broaden functionality while increasing the number of assets and operators a client must underwrite.

Exit, liquidity, and failure path

USDC withdrawal moves through the Arbitrum bridge, carries a fee, requires validator signatures and a dispute/finalization path. Other spot assets may depend on Unit or another independent route, and the official support material directs failed withdrawals to that team. A market sale depends on order-book depth for the exact pair; aggregate spot-orderbook TVL is not a bid for a long-tail HIP-1 token. Sending within Hyperliquid is not the same as withdrawing, and transfers to an address controlled by a nonintegrated exchange can leave only that exchange able to recover funds.

Comparison and decision

Eligible spot assets can be held natively or traded through a provider whose US legal and custody perimeter is separately approved. That avoids directing clients to an interface whose current terms prohibit them and can reduce the Hyperliquid bridge and validator layer. The rejection does not claim every HyperCore spot asset is defective; it says venue-level approval cannot substitute for asset eligibility and that this client population cannot use the offered interface. Reopen requires terms-based eligibility plus asset-by-asset and exit review.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Hyperliquid — Terms of Use · primary · accessed 2026-08-19
  Supports: United States restriction, interface eligibility
• Hyperliquid Docs — how to start trading · primary · accessed 2026-08-19
  Supports: spot workflow, deposits, USDC withdrawal
• Hyperliquid Docs — bridge · primary · accessed 2026-08-19
  Supports: validator signatures, withdrawal dispute, cold-wallet unlock
• Hyperliquid Docs — asset IDs · primary · accessed 2026-08-19
  Supports: spot assets, HIP-1 identifiers, outcomes
• Hyperliquid Support — withdrawal issues · primary · accessed 2026-08-19
  Supports: send versus withdraw, independent Unit bridge, failed withdrawal process
• DefiLlama — Hyperliquid Spot Orderbook protocol data · secondary · accessed 2026-08-19
  Supports: protocol category, chain perimeter, current TVL

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.