Routing

What a route means#

A route describes how an input asset can be exchanged for an output asset through integrated liquidity sources on Robinhood Chain. A route can contain one pool or multiple intermediate swaps. A quote can also divide the input across more than one route.

QuiverDex should compare the sources it actually supports. The phrase “every pool” is not appropriate unless coverage is measured and genuinely complete. A quoted outcome does not guarantee the best possible result across all venues.

Single-hop, multi-hop, and split routes#

A single-hop path trades directly from the input asset to the output asset. A multi-hop path uses one or more intermediate assets. A split route divides the input between multiple paths, then combines their output for the user.

A split is useful only when its estimated result justifies the additional costs and execution constraints. A one-path quote can be preferable. The interface must not force a split to earn points or make a diagram look more sophisticated.

Reading the route diagram#

The input asset appears on the left and the output asset on the right. Each path label names the integrated source and its share of the input. Line width is a visual aid; the percentage label is the precise value. A detail view should show all intermediate assets and pool identities.

An educational example might show Pool A — 55%, Pool B — 30%, and Pool C — 15%. These are illustrative names, not announced QuiverDex integrations. Live diagrams must use the actual quote response.

Comparing outcomes#

The intended comparison accounts for expected output, the product fee, applicable pool fees, and estimated network costs. Costs paid in different assets must not be subtracted twice or presented as though they share the same unit. A “saved” percentage requires a comparable, timestamped reference quote for the same amount and cost basis.

Price impact describes the estimated effect of the trade on available liquidity. Slippage tolerance defines the permitted change between the reviewed quote and execution. They are related but not interchangeable labels.

Quote freshness#

Quotes can change as pool state and costs change. Changing the amount, token pair, account, network, routing mode, or relevant settings requires a new quote. If a quote expires, refresh before signing. After a token approval, review a new quote rather than using old transaction data.

Swap execution and approvals#

If the deployed router supports atomic execution, required swap legs can be combined into a transaction that succeeds together or reverts. This is a contract behavior to verify, not a property established by a UI diagram.

Token spending permissions may still require separate wallet requests. ERC-20 defines allowances for third-party spending, and approval is not the same operation as a swap.^[1] A transaction that fails during on-chain execution can still incur network costs.^[2]

Limits and risks#

Simulations and estimates cannot eliminate contract, token, liquidity, or network risks. Multiple paths do not automatically mean independent failure domains. Do not assume a pool is never reused unless the actual algorithm enforces and documents that constraint.

See Fees for net-output semantics and Safety for permission review.