Guides

How MindSwap chooses a route

MindSwap compares supported route families, provider availability, and execution constraints before showing you a route set.

Published on 23 مارس 20264 min read

النقاط الرئيسية

1MindSwap surfaces only the route families that pass support and execution checks for the pair.
2Different pairs can return very different route sets.
3Users should evaluate route type and caveats, not just the quoted amount.

Short answer: MindSwap selects from the route families it can support for the pair at that moment, then filters the result set based on availability, execution requirements, and route checks.

Definition

MindSwap is a route-comparison surface. It can show private routes, same-network onchain DEX routes, gasless-capable routes, and cross-chain routes when those paths qualify for the requested pair.

What the route engine considers

Whether the pair is supported by the provider or onchain venue.
Whether the route is same-network or cross-chain.
Whether wallet signing or other execution prerequisites apply.
Whether current timing, quote freshness, and safety checks still pass.

When to use this knowledge

Use it when you need to understand why one quote surface shows multiple route families while another pair shows only one or none.

When not to over-assume

Do not assume a route family will always appear because it was available once. Route availability is live and pair-dependent.

Example

A same-network swap may return both a provider-backed route and an onchain DEX route, while a cross-chain pair may only return provider-backed paths. That difference is about route fit, not a universal preference for one model.

Caveats

The best route is not always the route with the highest displayed output. Users should still review route type, destination asset, timing caveats, and execution requirements.