PERP.WIKI

The Graph vs go-hyperliquid

Hyperliquid ecosystem comparison · Data APIs

Best for Research
Different Focus Areas

Quick Take

The Graph Decentralized indexing protocol for building GraphQL APIs from HyperEVM smart contracts on Multi-Layer, while go-hyperliquid Community Golang SDK for the Hyperliquid API with concurrent streaming support on Multi-Layer. They serve different niches in the Hyperliquid ecosystem.

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

Overview

The Graph logo

The Graph

The Graph is the decentralized indexing protocol for blockchain data, enabling HyperEVM developers to build and deploy Subgraphs—open APIs that index, transform, and serve on-chain data via GraphQL. Rather than building custom indexing infrastructure, HyperEVM protocol teams can define their data schema and indexing logic in a Subgraph manifest, and The Graph's decentralized network of Indexers handles the computation and data serving. This dramatically accelerates frontend development for Hyperliquid DeFi dApps that need historical and real-time on-chain data without running centralized backend infrastructure. Subgraph data is trustless and cryptographically verifiable, making it appropriate for decentralized applications that want to maintain censorship-resistance. The Graph's GRT token incentivizes high-quality, reliable data indexing, ensuring HyperEVM Subgraphs remain continuously available and accurate for users and developers building on Hyperliquid's smart contract ecosystem.

Visit website

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

Feature Comparison

FeatureThe Graph logoThe Graphgo-hyperliquid
LayerMulti-LayerMulti-Layer
CategoryData APIsSDKs & Developer Tools
StatusActiveActive
Launch Year
Websitethegraph.comgithub.com
Twitter
GitHubNot publicNot public
VerifiedUnverifiedUnverified
Tags

Score Comparison

The Graphgo-hyperliquid
Open Source
The Graph
Not public
go-hyperliquid
Not public
Verified
The Graph
Unverified
go-hyperliquid
Unverified
Ecosystem Breadth
The Graph
0 tags
go-hyperliquid
0 tags
Maturity
The Graph
Unknown
go-hyperliquid
Unknown

Feature Matrix

FeatureThe Graph logoThe Graphgo-hyperliquid
Open Source
Verified
Has Website
Has Twitter
Has GitHub
Active Status

Key Differences

Category Focus

The Graph is focused on data apis, while go-hyperliquid targets sdks & developer tools. They serve different user needs within the Hyperliquid ecosystem.

When to Use Each

Choose The Graph if you...

  • Want a data apis solution on Multi-Layer
  • Need: Decentralized indexing protocol for building GraphQL APIs from HyperEVM smart contracts

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

Ecosystem Integration

The Graph logo

The Graph

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

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.

Both protocols share the same layer, maximizing composability potential.

Community Verdict

Which do you prefer?

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

Related Comparisons