Across Protocol vs go-hyperliquid
Hyperliquid ecosystem comparison · Bridges & Cross-Chain
Ecosystem PickQuick Take
Across Protocol Intent-based cross-chain bridge — near-instant USDC bridging to Hyperliquid 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 Across Protocol and go-hyperliquid. Key differentiators: layer deployment, fee structure, liquidity depth, and community adoption. Last reviewed: Mar 2026.
Across Protocol
Multi-LayerIntent-based cross-chain bridge — near-instant USDC bridging to Hyperliquid
across.togo-hyperliquid
Multi-LayerCommunity Golang SDK for the Hyperliquid API with concurrent streaming support
github.comOverview
Across Protocol
Across Protocol is the leading intent-based cross-chain bridge, connecting over 15 chains — including Hyperliquid's HyperCore and HyperEVM — with near-instant settlement and some of the lowest fees in DeFi. Unlike traditional message-passing bridges, Across replaces step-by-step execution with user-declared outcomes called intents: users specify what they want, and a competitive network of relayers races to fulfill each transfer optimally. Backed by a three-layer architecture — a request-for-quote mechanism, a network of competitive relayers, and an on-chain settlement layer — Across guarantees fast fills averaging under one minute without sacrificing security or decentralization. Bridging 1 ETH costs under $1. The protocol has processed over $22B in cumulative volume across 15M+ transactions, making it one of the most proven interoperability solutions in production. For the Hyperliquid ecosystem, Across unlocks seamless capital inflows from Ethereum, Arbitrum, Base, Optimism, and beyond — giving users and protocols a reliable, low-cost on-ramp to both HyperCore's order-book liquidity and HyperEVM's growing DeFi landscape.
Visit websitego-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 websiteFeature Comparison
| Feature | go-hyperliquid | |
|---|---|---|
| Layer | Multi-Layer | Multi-Layer |
| Category | Bridges & Cross-Chain | SDKs & Developer Tools |
| Status | Active | Active |
| Launch Year | 2022 | — |
| Website | across.to | github.com |
| @AcrossProtocol | — | |
| GitHub | Not public | Not public |
| Verified | ✓ Verified | Unverified |
| Tags | bridgeintent-basedUSDCfast | — |
Score Comparison
Feature Matrix
| Feature | go-hyperliquid | |
|---|---|---|
| Open Source | ✗ | ✗ |
| Verified | ✓ | ✗ |
| Has Website | ✓ | ✓ |
| Has Twitter | ✓ | ✗ |
| Has GitHub | ✗ | ✗ |
| Active Status | ✓ | ✓ |
Key Differences
Category Focus
Across Protocol is focused on bridges & cross-chain, while go-hyperliquid targets sdks & developer tools. They serve different user needs within the Hyperliquid ecosystem.
When to Use Each
Choose Across Protocol if you...
- ✓Want a bridges & cross-chain solution on Multi-Layer
- ✓Prefer a verified and vetted protocol
- ✓Need features like bridge and intent-based
- ✓Need: Intent-based cross-chain bridge — near-instant USDC bridging to Hyperliquid
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
Across Protocol
Across Protocol 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 Across Protocol or go-hyperliquid to help others in the Hyperliquid community make better decisions.
Related Comparisons
Explore more projects in this category