Enso vs. HyperUnit (Unit)
Rift Research
Last updated
TLDR: Enso is a DeFi action and shortcut layer. HyperUnit (Unit) is a lock-and-mint bridge into Hyperliquid. Consider Enso when you need multi-step DeFi intents, not only a simple swap. Consider HyperUnit (Unit) when you want the purpose-built deposit path into Hyperliquid. Confirm the live winner on rates.gg.
What each protocol is
Enso. Enso is a unified DeFi API. The Route API finds a path into a destination token, LP or vault. The Bundle API composes ordered actions (swap, lend, borrow, deposit) into one transaction. Enso constructs transaction data for the integrating product to present for signing. The signing flow and underlying protocols determine permissions and custody assumptions. Official docs: Enso Docs. App: enso.finance.
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 | Enso | HyperUnit (Unit) |
|---|---|---|
| Role | DeFi action and shortcut layer | Lock-and-mint bridge into Hyperliquid |
| Fee | Depends on the composed route and underlying protocols | Network and deposit or withdrawal charges for the selected asset; check the current quote |
| Coverage | Multi-chain DeFi primitives connected through Enso integrations | Bitcoin, Ethereum, Solana, Base, Avalanche and other Unit-listed assets into Hyperliquid |
| Settlement | Atomic bundled transaction when using Bundle; otherwise the returned route tx | Lock on the native chain, credit on Hyperliquid |
| Trust model | Enso router / wallet adapters plus each underlying protocol | Guardian network and threshold signing; verify the current deployment’s signer assumptions |
| Good fit for | Multi-step DeFi intents, not only a simple swap | Direct deposits and withdrawals for Hyperliquid |
| Docs | Enso Docs | Unit Docs |
Where each fits
Enso may fit when:
- The job is swap-plus-deposit, zap, or another multi-step action
- You want Enso to build the calldata while you keep the wallet UX
- A single-hop bridge or AMM swap is not enough
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. Enso 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 Enso when you need multi-step DeFi intents, not only a simple swap.
- 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, Enso or HyperUnit (Unit)?
Neither has a universal price advantage. Enso: Depends on the composed route and underlying protocols. 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 Enso 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 Enso and HyperUnit (Unit) docs?
Enso: Enso Docs. HyperUnit (Unit): Unit Docs. Live rate comparison: rates.gg.
Official sources
- Enso docs: Enso Docs
- Enso app: enso.finance
- Enso — Developer home: docs.enso.build/home
- Enso — Use cases: docs.enso.build/pages/use-cases
- Enso — API: api.enso.finance/api
- 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 Enso 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.