go-hyperliquid vs Mizu
Hyperliquid ecosystem comparison · SDKs & Developer Tools
Ecosystem PickQuick Take
go-hyperliquid Community Golang SDK for the Hyperliquid API with concurrent streaming support on Multi-Layer, while Mizu Unified liquidity layer and yield aggregator for HyperEVM on HyperEVM. They serve different niches in the Hyperliquid ecosystem.
Based on public data for go-hyperliquid and Mizu. Key differentiators: layer deployment, fee structure, liquidity depth, and community adoption. Last reviewed: Mar 2026.
go-hyperliquid
Multi-LayerCommunity Golang SDK for the Hyperliquid API with concurrent streaming support
github.comMizu
HyperEVMUnified liquidity layer and yield aggregator for HyperEVM
mizulabs.xyzOverview
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 websiteMizu
Mizu Labs is an automated yield aggregator protocol deployed on HyperEVM, Hyperliquid's EVM-compatible smart contract layer. Designed for ETH and BTC holders seeking to maximize returns within the Hyperliquid ecosystem, Mizu issues liquid wrapper tokens — hypeETH and hypeBTC — representing bridged assets that are continuously deployed across the highest-yielding HyperEVM protocols. Under the hood, Mizu automates liquidity routing into established platforms including HyperLend, HypurrFi, Felix, and Harmonix, compounding rewards and rebalancing positions without requiring manual intervention from depositors. This set-and-forget approach makes Mizu ideal for users who want exposure to HyperEVM's rich DeFi landscape — spanning lending markets, stablecoin minting, and structured yield products — without the overhead of active position management. By aggregating liquidity from many depositors, Mizu accesses yield opportunities at scale that would be inefficient for individual wallets. The protocol participates in points programs across its integrated protocols, passing accumulated rewards back to hypeETH and hypeBTC holders. As HyperEVM matures as a composable DeFi layer beneath Hyperliquid's core trading infrastructure, Mizu Labs positions itself as the primary yield optimization engine for bridged capital seeking productive, automated deployment.
Visit websiteFeature Comparison
| Feature | go-hyperliquid | |
|---|---|---|
| Layer | Multi-Layer | HyperEVM |
| Category | SDKs & Developer Tools | Yield & Vaults |
| Status | Active | Active |
| Launch Year | — | 2025 |
| Website | github.com | mizulabs.xyz |
| — | @mizulabs | |
| GitHub | Not public | Not public |
| Verified | Unverified | Unverified |
| Tags | — | yield-aggregatorvaultsmulti-assetBoringVault |
Score Comparison
Feature Matrix
| Feature | go-hyperliquid | |
|---|---|---|
| Open Source | ✗ | ✗ |
| Verified | ✗ | ✗ |
| Has Website | ✓ | ✓ |
| Has Twitter | ✗ | ✓ |
| Has GitHub | ✗ | ✗ |
| Active Status | ✓ | ✓ |
Key Differences
Layer Architecture
go-hyperliquid operates on Multi-Layer (spans multiple hyperliquid layers), while Mizu runs on HyperEVM (evm smart contracts on hyperliquid l1). This affects composability, transaction speed, and the types of integrations each protocol supports.
Category Focus
go-hyperliquid is focused on sdks & developer tools, while Mizu targets yield & vaults. 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 Mizu if you...
- ✓Want a yield & vaults solution on HyperEVM
- ✓Need features like yield-aggregator and vaults
- ✓Need: Unified liquidity layer and yield aggregator for HyperEVM
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.
Mizu
Mizu operates on HyperEVM (evm smart contracts on hyperliquid l1). As a HyperEVM protocol, it can compose with other EVM-based DeFi primitives and leverage smart contract flexibility.
Community Verdict
Which do you prefer?
Share your experience with go-hyperliquid or Mizu to help others in the Hyperliquid community make better decisions.
Related Comparisons
Explore more projects in this category