NEAR Intents vs. HyperUnit (Unit)
Rift Research
Last updated
TLDR: NEAR Intents is a multichain intent and solver network. HyperUnit (Unit) is a lock-and-mint bridge into Hyperliquid. Consider NEAR Intents when you need unusual pairs, non-EVM routes, or solver-sourced liquidity. Consider HyperUnit (Unit) when you want the purpose-built deposit path into Hyperliquid. Confirm the live winner on rates.gg.
What each protocol is
NEAR Intents. NEAR Intents is a multichain intent protocol. You specify the outcome (asset in, asset out, destination). Market makers compete to fill it. The verifier contract settles intent batches on NEAR. Cross-chain deposits and withdrawals use token bridges, with their own settlement and refund conditions. Official docs: NEAR Intents Docs. App: near-intents.org.
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 | NEAR Intents | HyperUnit (Unit) |
|---|---|---|
| Role | Multichain intent + solver network | Lock-and-mint bridge into Hyperliquid |
| Fee | Solver spread set in the winning quote | Network and deposit or withdrawal charges for the selected asset; check the current quote |
| Coverage | Bitcoin, EVM chains, Solana, NEAR, TON, Sui, Stellar and other listed assets | Bitcoin, Ethereum, Solana, Base, Avalanche and other Unit-listed assets into Hyperliquid |
| Settlement | Atomic via the intents verifier on NEAR | Lock on the native chain, credit on Hyperliquid |
| Trust model | Verifier contract on NEAR, solver liquidity, and the token bridges used for deposits and withdrawals | Guardian network and threshold signing; verify the current deployment’s signer assumptions |
| Good fit for | Unusual pairs, non-EVM routes, and solver-sourced liquidity | Direct deposits and withdrawals for Hyperliquid |
| Docs | NEAR Intents Docs | Unit Docs |
Where each fits
NEAR Intents may fit when:
- The pair or chain sits outside most EVM-only aggregators
- You want solvers competing on a signed intent
- Native settlement across non-EVM ecosystems matters
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. NEAR Intents 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 NEAR Intents when you need unusual pairs, non-EVM routes, or solver-sourced liquidity.
- 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, NEAR Intents or HyperUnit (Unit)?
Neither has a universal price advantage. NEAR Intents: Solver spread set in the winning quote. 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 NEAR Intents 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 NEAR Intents and HyperUnit (Unit) docs?
NEAR Intents: NEAR Intents Docs. HyperUnit (Unit): Unit Docs. Live rate comparison: rates.gg.
Official sources
- NEAR Intents docs: NEAR Intents Docs
- NEAR Intents app: near-intents.org
- NEAR Intents — What are intents?: docs.near-intents.org/getting-started/what-are-intents
- NEAR Intents — NEAR chain-abstraction overview: docs.near.org/chain-abstraction/intents/overview
- NEAR Intents — 1-Click Swap API: docs.near-intents.org/
- 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 NEAR Intents 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.