Most swap interfaces optimize for one thing: the quoted output.
But a quote is only a prediction. It does not tell you whether the final calldata will execute, whether the route will revert, how much gas it will consume, or whether the transaction still enforces the parameters the user reviewed.
Route is designed around the complete execution path.
For every request, Route discovers liquidity across verified Robinhood Chain pools and builds up to 32 candidate paths from a bounded set of 96 pools. Paths can contain up to three hops. The optimizer also considers as many as three disjoint split branches, using a 10% allocation grid followed by 1% local refinement.
Partial-capacity sampling matters here. The best pool for an entire order is not necessarily the best pool for part of it. Route samples different allocations, rejects split branches that reuse the same liquidity, and scores the resulting combinations without pretending the bounded search is a mathematical global optimum.
Direct routing currently covers Uniswap V2, V3, hookless V4 and GIGA CL. Route can also evaluate guarded upstream candidates from KyberSwap and, when enabled, 0x. These are treated as separate providers - not mislabeled as native Route integrations.
Provider requests run in parallel, successful duplicates are merged, and upstream plan construction overlaps with the direct search. Prices and pool state are request-scoped: no completed quote or price survives into another request or block.
The important difference comes after discovery.
Route constructs the actual transaction for each final candidate and runs both eth_call and estimateGas against a shared block using the same execution gas-price context. Candidates that revert are removed. Successfully simulated candidates take priority over quote-only fallbacks.
When gas can be converted into the output token using a common reference, Route ranks candidates by:
simulated output − estimated execution gas
That prevents a nominally larger quote from automatically winning when its execution path consumes enough additional gas to erase the advantage.
Settlement is independently constrained onchain. The executor enforces the exact input, actual received output, signed minimum output, recipient and deadline. Temporary approvals are cleared. Upstream calldata is validated against fixed targets and selectors, and Route does not silently substitute a different provider or approval spender after review.
We studied execution-time routing systems such as DFlow’s JIT model, which can re-evaluate proprietary AMM pricing inside the transaction. Route built and tested a narrower experimental two-path JIT prototype, but it is not part of the active product. The live system performs execution-aware selection before signing; it does not claim DFlow parity or execution-time rerouting.
Route also does not claim a global best price, universal MEV protection, guaranteed fills or audited security.
What it does provide is a bounded, inspectable routing system that evaluates executable transactions, not just quote responses and preserves the user’s reviewed constraints through settlement.
In all honesty, I saw @LadyExchange_ tried it out and some of the routing just didn't function. So I built this to use for myself and decided to see how far I can push this.
Route charges 0 bps. Pool fees, upstream-provider charges and network gas still apply.
Go ahead and try it out now auth is powered by @dynamic_xyz
