Docs

• Router — reads your balances on every network and gathers them into the one asset and network you pick.
• Swap / Bridge — Swap turns one asset into another on the same network; Bridge sends one asset, all of it or only part, to another network.
• Balances — what the wallet, or the address you watch, holds on each network, and whether each balance can be moved.
• Activity — every route you ran, grouped runs, rollup withdrawals, and USDC transfers that were sent but never finished.
• Bridges / Faucets — help from outside RouteDust: each network's own bridge site, and the faucets that hand out test funds, easiest first. Tags say what a faucet asks for (an account, a balance on mainnet, a captcha, a social login, or real money when it is marked Paid). They open in a new tab and nothing is claimed for you.
• Network — Networks lists every testnet with its gas asset and lets you add it to your wallet; Protocols shows which bridges and exchanges are answering right now; Coverage shows which testnets each of them supports; Liquidity creates a pool for your own token; and Status says whether the services RouteDust relies on are up.
• Settings — what “best route” means to you, your slippage and price-impact limits, your own network endpoints and the theme. Everything stays in this browser.

Gas asset. Every network charges fees in its own asset. On most of the 20 testnets here that is ETH, elsewhere MON, AVAX, POL, SEI, INJ and others. Arc is the odd one: there you pay fees in USDC. You always need a little of the network's own asset before anything can move.

Wrapped. The tradable version of a gas asset (WETH for ETH, WMON for MON). Pools trade the wrapped one; RouteDust wraps and unwraps for you and, by default, hands you the real gas asset at the end rather than the wrapped copy.

Not every USDC is the same USDC. USDC issued by Circle on a network, a bridged copy of it and a test token that merely calls itself USDC are different things. Routes keep them apart, so the target you pick is the one you get.

Dust. The small leftovers faucets and tests spread across networks. Alone they are too small to be worth a transfer; gathered into one asset on one network they become usable again.

Route. The steps needed to turn one balance into your target: a swap, a bridge, sometimes both. Every step has to be live at that moment, with a real price, or the route is not offered.

Watching an address. Paste any address, or open a link ending in ?watch=0x…, to see its balances and routes without connecting a wallet. Nothing can be signed while watching, and a connected wallet always takes over. Each browser tab keeps its own wallet or watched address.

RouteDust moves nothing itself. It uses the networks' own bridges and exchanges, and every card says which one it would use before you sign.

• Circle CCTP — the official way to move USDC between networks: burned on one side, minted on the other, so you receive real USDC and not a wrapper. Usually a minute or two. Either you submit the final step yourself, which needs a little gas on the destination, or Circle submits it for you for a small fee.
• Circle Gateway — deposit USDC once per network, then one signature moves all of it at once. Worth it when several networks hold USDC. The deposit has to settle first: seconds on Arc and the fast networks, about fifteen minutes on Sepolia.
• Uniswap and other exchanges — for turning one asset into another on the same network. Only pools that really hold liquidity are used, and the price impact of your own amount is always shown.
• Hyperlane, Stargate, Across, LI.FI and the Optimism bridge — alternatives for ETH and USDC, each with its own speed and cost. They deliver without gas on the destination, and on testnets they are best effort: when one is not answering, its routes are simply not offered. Across does not refund a testnet deposit that no relayer fills, so keep those amounts small; a route that would hand back less than half of the best one is not shown at all.
• Each network's own bridge — where a network runs a bridge site of its own, or its documentation sends you to one, Bridge and Networks link it with the direction already chosen, and Bridges / Faucets lists all of them. RouteDust does not sign anything there; it is simply the way across when no live route exists.

Which provider is answering right now is on Protocols; what each network supports is on Coverage.

For every balance, in this order: keep back enough gas for the transactions that route will need, find the ways it could reach your target, price each of them for real, and keep the best one.

You decide what “best” means. Best output keeps the most on the target. Fewest transactions asks for as few wallet prompts as possible. Fastest prefers the quickest path. Native only refuses to leave you holding a wrapped token. Max coverage tries to move as many balances as it can. Switching between them is instant.

Compact or detailed. The Router shows every route as a full card (amount presets, alternatives, why this route) or, in Compact, as one row each: what leaves, who carries it, what arrives. Your choice is remembered, and so is the plan: moving to another page and back does not scan or plan again. Rescan when you want fresh balances.

Too big for the pool. If converting the whole balance would move the price further than your limit (5% by default, in Settings), the route is offered for the amount that fits and marked PARTIAL, with the reason on the card. Nothing is dumped into a thin pool on your behalf.

Several balances on one network can travel together: they are gathered into one asset first, then a single bridge carries the total. Fewer signatures, and the bridge fee is paid once.

One transfer instead of a sweep. The Router gathers everything into one target. To send one asset, or only part of it, from one network to another, use Swap → Bridge: pick the two networks and an amount (a percentage or your own number), and every live way between them is priced, with the best one preselected. For the gas asset, the fee for the transfer itself is kept back.

“No route” is a real answer. When a network has no gas, no pool or no live bridge, the card says which of those it was, and links the faucets when gas is what is missing, or the network's own bridge when that is the only way across.

• You sign every transaction in your own wallet. RouteDust never holds your keys and cannot move anything on its own.
• Approvals are for the exact amount that step needs, to the contract that step uses. Never unlimited, never to an address you have not seen on the card.
• Every transaction is tried against the network before it reaches your wallet: one that would fail is not put in front of you, and the prompt is explained in plain words first.
• The cost is compared with your balance beforehand, so a route does not stop halfway because gas ran out.
• Contracts are remembered between runs. If one is replaced by a different one, you are told before you sign.
• A bridge transfer is never sent twice. After an interruption RouteDust looks for the transaction on the network and continues from it; when it cannot tell, it stops and asks you instead of guessing. A transaction you paste there must come from your wallet and call that step's contract.
• A route runs in one place at a time. Leaving its page and coming back, or opening it in a second tab, never starts it again while a wallet prompt is still open; the other tab says where it is running.
• Prices are fetched again right before each step. If the new price is worse than what you accepted when the route was planned, nothing is sent until you choose the new price yourself.
• A transaction that was mined but failed moved nothing except its gas. Retry builds that step again at the current price instead of repeating the one that failed.
• Disconnecting your wallet only pauses a route, nothing fails on-chain. Reconnect and press Resume.
• Your history stays in this browser and is archived, never deleted. Every tab sees the same history and settings, while each keeps its own wallet or watched address and its own balances, so two tabs never undo each other. A full browser storage never interrupts a route that is running. Activity can also find transfers that were sent but never arrived and finish them.
• When you add liquidity, the transaction carries minimum amounts at the current price, so it cannot fill at a price someone else set a moment earlier.

• The wallet asks to switch network: approve it. If your wallet does not know the testnet yet, RouteDust adds it first with a working endpoint; you can also do that from Networks.
• Needs gas: the card names the network and links its faucets; every faucet is on Bridges / Faucets. Top up, then press Retry.
• The price moved between the quote and your signature: the transaction is refused before it can take anything. Retry prices it again; the tolerance is in Settings.
• The price moved since the route was planned: the route stops before signing and shows the new price. Press “Accept the new price and continue” if it is still worth it, or plan again later.
• A transaction reverted: it was mined but did nothing apart from using gas. Retry builds that step again with a fresh price.
• “Running in another tab”: the route is already running elsewhere in this browser. Continue it there; this page lets you press Resume again once it stops.
• A network's RPC is slow or down: add your own endpoint in Settings. It is saved only after it answers for the right network, and the public endpoints stay behind it as a fallback.
• Only part of the balance is routable: converting the rest would move the pool too far. Route it in parts, pick a target that needs no conversion (USDC to USDC only bridges), or raise the limit in Settings and accept the loss.
• “The wallet holds less than the route was planned for”: the balance changed after the plan was made. Rescan on the Router page and plan again.
• Sent but not arrived: Activity → Circle USDC burns on-chain → Scan finds USDC transfers that were never finished and lets you complete them, even from an old route.
• A network with no way out: a few testnets have no bridge, no pool and no Circle USDC, so no route can move a balance off them. Bridge, Networks and Bridges / Faucets link the network's own bridge where there is one. For a rollup what is left is the network's own withdrawal, which takes about a week. Activity tracks those under “Rollup withdrawals”: start one there, and it tells you when each of the two Ethereum Sepolia steps (prove, then finalise) is due and signs them. A withdrawal you started in another bridge can be tracked by pasting its transaction. Until it is finalised the ETH is still yours, waiting in the rollup's contract on Sepolia.
• A Gateway deposit is still waiting: Circle credits it only once the network settles. Until you sign, that USDC is still yours and can be withdrawn.

A route can also explain itself: open it and press “Why this route?” to see where each step's data came from. The source code is public.