PERP.WIKI

go-hyperliquid vs Hyperbloom

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 Hyperbloom DEX aggregator and autocompounding yield optimizer on HyperEVM. They serve different niches in the Hyperliquid ecosystem.

Based on public data for go-hyperliquid and Hyperbloom. 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
Hyperbloom logo

Hyperbloom

HyperBloom is a DeFi SuperApp built on HyperEVM that combines a DEX aggregator with auto-compounding yield vaults, delivering best-in-class swap rates and maximized APYs across the Hyperliquid ecosystem. Its aggregator routes trades through a unified smart contract that covers liquidity from 10 integrated DEXs — including HyperSwap, KittenSwap, Curve, Laminar, Gliquid, Hybra, HyperCat, ProjectX, Valantis, and Ramses — plus HyperCore order-book depth, all settled in a single non-custodial transaction with no custody risk. For yield seekers, HyperBloom's auto-compounding vaults employ a proprietary YieldIQ strategy: on-chain algorithms that dynamically optimize liquidity positions, compound rewards continuously, and minimize unnecessary rebalancing and gas costs. Vaults support single-token deposits, eliminating the complexity of fixed 50/50 LP ratios and letting users retain directional preference over their underlying assets. Vault tokens represent proportional claims on deposits plus accumulated yield, redeemable at any time. HyperBloom also features a liquidity locker, a developer-facing widget API, and a points program — making it a comprehensive infrastructure layer for traders, LPs, and protocols building on HyperEVM.

Visit website

Feature Comparison

Featurego-hyperliquidHyperbloom logoHyperbloom
LayerMulti-LayerHyperEVM
CategorySDKs & Developer ToolsYield & Vaults
StatusActiveActive
Launch Year2025
Websitegithub.comhyperbloom.xyz
Twitter@hyperbloomxyz
GitHubNot publicNot public
VerifiedUnverifiedUnverified
Tags
DEX-aggregatoryieldautocompounding

Score Comparison

go-hyperliquidHyperbloom
Open Source
go-hyperliquid
Not public
Hyperbloom
Not public
Verified
go-hyperliquid
Unverified
Hyperbloom
Unverified
Ecosystem Breadth
go-hyperliquid
0 tags
Hyperbloom
3 tags
Maturity
go-hyperliquid
Unknown
Hyperbloom
Since 2025

Feature Matrix

Featurego-hyperliquidHyperbloom logoHyperbloom
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 Hyperbloom 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 Hyperbloom 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 Hyperbloom if you...

  • Want a yield & vaults solution on HyperEVM
  • Need features like DEX-aggregator and yield
  • Need: DEX aggregator and autocompounding yield optimizer

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.

Hyperbloom logo

Hyperbloom

Hyperbloom 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 Hyperbloom to help others in the Hyperliquid community make better decisions.

Related Comparisons