Relay vs. HyperUnit (Unit)
Rift Research
Last updated
TLDR: Relay is a cross-chain intents and payments protocol. HyperUnit (Unit) is a lock-and-mint bridge into Hyperliquid. Consider Relay when you need fast small-to-mid transfers and payments across many networks. Consider HyperUnit (Unit) when you want the purpose-built deposit path into Hyperliquid. Confirm the live winner on rates.gg.
What each protocol is
Relay. Relay is a cross-chain intents protocol. Users deposit into a per-chain Depository; solvers fill on the destination; a dedicated settlement chain and oracle reimburse the solver. Official docs: Relay Docs. App: relay.link.
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 | Relay | HyperUnit (Unit) |
|---|---|---|
| Role | Cross-chain intents and payments protocol | Lock-and-mint bridge into Hyperliquid |
| Fee | Solver spread plus small protocol components, quoted per order | Network and deposit or withdrawal charges for the selected asset; check the current quote |
| Coverage | Networks and assets supported by the selected Relay route | Bitcoin, Ethereum, Solana, Base, Avalanche and other Unit-listed assets into Hyperliquid |
| Settlement | Solver fronts destination liquidity; protocol settles after proof | Lock on the native chain, credit on Hyperliquid |
| Trust model | Non-upgradable Depository contracts; Allocator-authorised withdrawals; audited settlement stack | Guardian network and threshold signing; verify the current deployment’s signer assumptions |
| Good fit for | Fast small-to-mid transfers and payments across many networks | Direct deposits and withdrawals for Hyperliquid |
| Docs | Relay Docs | Unit Docs |
Where each fits
Relay may fit when:
- Speed on a small or mid-size transfer matters most
- You need a long list of networks from one integration
- The job is a payment or simple transfer, not a multi-step DeFi action
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. Relay 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 Relay when you need fast small-to-mid transfers and payments across many networks.
- 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, Relay or HyperUnit (Unit)?
Neither has a universal price advantage. Relay: Solver spread plus small protocol components, quoted per order. 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 Relay 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 Relay and HyperUnit (Unit) docs?
Relay: Relay Docs. HyperUnit (Unit): Unit Docs. Live rate comparison: rates.gg.
Official sources
- Relay docs: Relay Docs
- Relay app: relay.link
- Relay — How Relay works: docs.relay.link/how-relay-works
- Relay — Protocol design: docs.relay.link/references/protocol/how-it-works
- Relay — Security and audits: docs.relay.link/references/protocol/security
- 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 Relay 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.