Across vs. HyperUnit (Unit)
Rift Research
Last updated
TLDR: Across is an intent-based interoperability protocol. HyperUnit (Unit) is a lock-and-mint bridge into Hyperliquid. Consider Across when you are moving canonical USDC or ETH between major chains and care about speed. Consider HyperUnit (Unit) when you want the purpose-built deposit path into Hyperliquid. Confirm the live winner on rates.gg.
What each protocol is
Across. Across is an intents protocol for bridging and cross-chain swaps. Relayers front destination liquidity. Across advertises approximately two-second fills on supported mainnet routes; actual timing depends on the route. Its intent settlement and refund mechanisms are separate from that initial fill. Official docs: Across Docs. App: across.to.
HyperUnit (Unit). Unit (HyperUnit) deposits native assets into Hyperliquid spot via a guardian MPC network. It is purpose-built for HyperCore deposits and withdrawals, not a general cross-chain aggregator. Official docs: Unit Docs. App: app.hyperunit.xyz.
Short version
| Dimension | Across | HyperUnit (Unit) |
|---|---|---|
| Role | Intent-based interoperability protocol | Lock-and-mint bridge into Hyperliquid |
| Fee | Market-quoted relayer spread and LP fee; no separate flat protocol toll | Network and deposit or withdrawal charges for the selected asset; check the current quote |
| Coverage | Supported mainnet networks, with availability determined by the exact token pair and route | Bitcoin, Ethereum, Solana, Base, Avalanche and other Unit-listed assets into Hyperliquid |
| Settlement | Canonical assets delivered by bonded relayers | Lock on the native chain, credit on Hyperliquid |
| Trust model | Relayer-funded fills and the settlement and dispute mechanisms of the deployed Across contracts | Guardian network and threshold signing; verify the current deployment’s signer assumptions |
| Good fit for | Canonical USDC and ETH transfers between supported chains | Direct deposits and withdrawals for Hyperliquid |
| Docs | Across Docs | Unit Docs |
Where each fits
Across may fit when:
- You are moving USDC or ETH between major supported chains
- Fast destination fills matter; confirm the estimate for your route
- You want a dedicated intent rail rather than a meta-aggregator
HyperUnit (Unit) may fit when:
- The only job is moving a Unit-supported asset onto or off Hyperliquid
- You accept the guardian MPC trust model
Key differences
Unit is designed for deposits and withdrawals of supported assets into Hyperliquid spot. Across has a different trading or routing scope. Compare them only where both can deliver the same asset and destination. Include any extra spot trade, bridge charge and confirmation wait. Check Unit’s current deposit minimums before funding an address.
When to use which
- Use Across when you are moving canonical USDC or ETH between major chains and care about speed.
- Use HyperUnit (Unit) when you want the purpose-built deposit path into Hyperliquid.
- If both can quote the same route, take the better net output after fees, time and settlement type. Check that print on rates.gg.
FAQ
Which is cheaper, Across or HyperUnit (Unit)?
Neither has a universal price advantage. Across: Market-quoted relayer spread and LP fee; no separate flat protocol toll. HyperUnit (Unit): Network and deposit or withdrawal charges for the selected asset; check the current quote. Compare executable quotes for the same size, destination and time window, including gas, underlying venue costs and any extra transfer. Expected output and minimum received are different figures; compare like with like.
Is Across a substitute for HyperUnit (Unit)?
Only on overlapping pairs and chains. When both can quote the same route, take the better net output after fees and time. When only one supports the asset or chain, that one is the only option.
Where are the official Across and HyperUnit (Unit) docs?
Across: Across Docs. HyperUnit (Unit): Unit Docs. Live rate comparison: rates.gg.
Official sources
- Across docs: Across Docs
- Across app: across.to
- Across — Introduction: docs.across.to/introduction
- Across — Features and fill times: docs.across.to/introduction/features
- Across — API reference: docs.across.to/api-reference
- HyperUnit (Unit) docs: Unit Docs
- HyperUnit (Unit) app: app.hyperunit.xyz
- HyperUnit (Unit) — Architecture: docs.hyperunit.xyz/architecture/components
- HyperUnit (Unit) — Supported assets and minimums: docs.hyperunit.xyz/unit/about-unit/supported-assets
- HyperUnit (Unit) — API and confirmations: docs.hyperunit.xyz/developers/api
Get the Best of Both With Rift
Rift is a strong alternative to choosing between Across and HyperUnit (Unit). It brings routes from both together with additional venues on supported pairs, comparing available quotes to find the best net execution for your order. You get the strengths of both through one API.
Rift adds no router fee and uses secure hardware enclaves to enforce noncustodial execution. Underlying venue fees, spreads and network costs still apply, and availability depends on the asset, chain and order size. The live quote shows the route and expected output.