How it works

Scan → Discover → Quote → Simulate → Sign · 20 testnets · every step verifiable

01Scan

Balances are read from public RPCs in your browser for every registry chain: native gas, wrapped native and Circle USDC (plus the issuer test tokens and, when enabled, ERC-20s an indexer lists). Nothing is sent to a server.

02Discover

Every provider is asked what it can do right now: Uniswap pools with liquidity and a probe quote, CCTP domains with bytecode on both sides, Across and LI.FI route lists, Hyperlane and Gateway contracts verified on-chain. "Protocol supports chain X" is never enough for an edge.

03Quote

For each balance the planner walks the capability graph (shortest paths first), quotes every hop with the amount that actually arrives, reserves gas on every chain a step touches, and keeps the best route per mode. Provider caps and thin pools become PARTIAL routes instead of failures.

04Simulate

Before the wallet is asked to sign, each transaction is eth_call-simulated, gas is estimated on our RPC (plus the L2 data fee), the spender's bytecode hash is compared with the pinned one, and the exact calldata is summarised in plain words.

05Sign and track

Your wallet signs one transaction at a time. Cross-chain steps are polled (Circle attestations, relayers, LayerZero Scan). A burn is never sent twice: if the wallet's nonce moved, the transaction is found on-chain or the route stops and asks you.

Non-negotiable rules

Native is a role, not ETHMON, AVAX, POL, S, SEI, TCRO, XPL, OKB and INJ are gas assets in their own right; wrapped versions are separate assets.

Asset identity is chain + address + representationCircle-native USDC, a bridged USDC and a wrapped native are different nodes in the graph even when the symbol matches.

Deployment is not liquidityA DEX contract being deployed proves nothing; only a pool with liquidity and a successful probe quote becomes a swap edge.

Every executable route has a live quoteQuotes expire; expired ones are re-quoted, never reused.

Gas is reserved before conversionNative balances keep enough for the route's own transactions, including destination claims and relayer fees.

"No route" is a correct answerWhen nothing is executable the app says so and explains what each provider replied.

Every route explains itselfEach edge carries where its data came from (official registry, on-chain probe, runtime API) and when it was verified.

The full reference (concepts, adding a chain, writing an adapter, the security model, troubleshooting) is in Docs.