3.2 - Routing & Errors
How the router finds best execution — and what to do when swaps fail.
The nest router automatically searches across all available pools to find the most efficient execution path for your swap. A trade may route through multiple pools (multi-hop) if that delivers a better net output than a single direct swap.
How routing works
You request a swap from Token A → Token B
The router scans all available paths: direct A→B, A→USDH→B, A→WHYPE→B, and more
It selects the path that maximises your output after all fees
The route is shown in the swap interface before you confirm
HYPE → TOKEN may route as HYPE → USDH → TOKEN if that path has deeper liquidity and lower total price impact — even though it uses two pools and two fee hops.
When routing looks unexpected
The direct pool may have low liquidity → multi-hop is better
New or low-liquidity tokens may route imperfectly until liquidity deepens
If the route looks very inefficient: reduce size and retry, or wait for more liquidity
Common Swap Errors
Insufficient output / Slippage exceeded
Price moved outside your slippage tolerance
Increase slippage slightly or reduce trade size
Insufficient gas
Not enough HYPE in wallet for gas
Add HYPE to your wallet — HYPE is the gas token on HyperEVM
Approval required
Token hasn't been approved for the router
Approve the token (first time only per token)
Transaction reverted
Slippage, gas, or pool state changed
Refresh and retry; check slippage and gas
Route not found
No liquidity path exists for this pair
Try routing manually through USDH or WHYPE, or wait for liquidity
Most common issue: not enough HYPE for gas. Always keep some HYPE in your wallet on HyperEVM — even a small amount covers most transactions.
Last updated