PERP.WIKI

go-hyperliquid vs Hyperliquid Spot

Hyperliquid ecosystem comparison · SDKs & Developer Tools

Ecosystem Pick
Different Focus Areas

Quick Take

go-hyperliquid Community Golang SDK for the Hyperliquid API with concurrent streaming support on Multi-Layer, while Hyperliquid Spot Native on-chain order book spot trading with HIP-1 and HIP-2 token standards on Multi-Layer. They serve different niches in the Hyperliquid ecosystem.

Based on public data for go-hyperliquid and Hyperliquid Spot. Key differentiators: layer deployment, fee structure, liquidity depth, and community adoption. Last reviewed: Mar 2026.

Overview

go-hyperliquid

go-hyperliquid is a community-developed Golang SDK for the Hyperliquid API, providing idiomatic Go bindings for trading, market data, and account management on Hyperliquid. Built with Go's concurrency model in mind, the SDK leverages goroutines and channels for efficient WebSocket streaming and concurrent order management—making it well-suited for high-throughput trading systems written in Go. The library covers the full Hyperliquid API including REST endpoints for order placement, account queries, and historical data, as well as WebSocket subscriptions for real-time order book updates and trade feeds. With typed request and response structures, comprehensive error handling, and context-aware API calls, go-hyperliquid provides the idiomatic Go developer experience that the Hyperliquid ecosystem previously lacked, enabling the large Go trading infrastructure community to build on Hyperliquid. The SDK has active contributors and is maintained alongside the official Python and Rust SDKs.

Visit website
Hyperliquid Spot logo

Hyperliquid Spot

Hyperliquid's native spot order book is the on-chain spot trading layer of the Hyperliquid L1, enabling permissionless listing and trading of tokens through the HIP-1 and HIP-2 token standards. Unlike AMM-based spot trading, Hyperliquid Spot uses a fully on-chain central limit order book (CLOB) with 200k orders per second throughput, delivering CEX-equivalent matching engine performance for spot assets. HIP-1 provides the fungible token standard analogous to ERC-20, while HIP-2 governs hyperliquidity provision—requiring token deployers to seed initial order book liquidity. Tokens launched through this mechanism trade natively on Hyperliquid's CLOB alongside the perp markets, creating a unified liquidity environment. The native spot DEX has become the go-to venue for launching and trading Hyperliquid-native tokens like PURR, HYPE, and the growing list of HyperEVM-native project tokens, with billions in cumulative spot trading volume demonstrating strong adoption.

Visit website

Feature Comparison

Featurego-hyperliquidHyperliquid Spot logoHyperliquid Spot
LayerMulti-LayerMulti-Layer
CategorySDKs & Developer ToolsDecentralized Exchanges
StatusActiveActive
Launch Year
Websitegithub.comapp.hyperliquid.xyz
Twitter
GitHubNot publicNot public
VerifiedUnverifiedUnverified
Tags

Score Comparison

go-hyperliquidHyperliquid Spot
Open Source
go-hyperliquid
Not public
Hyperliquid Spot
Not public
Verified
go-hyperliquid
Unverified
Hyperliquid Spot
Unverified
Ecosystem Breadth
go-hyperliquid
0 tags
Hyperliquid Spot
0 tags
Maturity
go-hyperliquid
Unknown
Hyperliquid Spot
Unknown

Feature Matrix

Featurego-hyperliquidHyperliquid Spot logoHyperliquid Spot
Open Source
Verified
Has Website
Has Twitter
Has GitHub
Active Status

Key Differences

Category Focus

go-hyperliquid is focused on sdks & developer tools, while Hyperliquid Spot targets decentralized exchanges. They serve different user needs within the Hyperliquid ecosystem.

When to Use Each

Choose go-hyperliquid if you...

  • Want a sdks & developer tools solution on Multi-Layer
  • Need: Community Golang SDK for the Hyperliquid API with concurrent streaming support

Choose Hyperliquid Spot if you...

  • Want a decentralized exchanges solution on Multi-Layer
  • Need: Native on-chain order book spot trading with HIP-1 and HIP-2 token standards

Ecosystem Integration

go-hyperliquid

go-hyperliquid operates on Multi-Layer (spans multiple hyperliquid layers). Spanning multiple layers lets it combine the strengths of each, though integration complexity is higher.

Hyperliquid Spot logo

Hyperliquid Spot

Hyperliquid Spot operates on Multi-Layer (spans multiple hyperliquid layers). Spanning multiple layers lets it combine the strengths of each, though integration complexity is higher.

Both protocols share the same layer, maximizing composability potential.

Community Verdict

Which do you prefer?

Share your experience with go-hyperliquid or Hyperliquid Spot to help others in the Hyperliquid community make better decisions.

Related Comparisons