KyberSwap cross-chain swaps: provider and route checks

KyberSwap's cross-chain interface compares third-party routes. Choosing it does not mean that KyberSwap itself operates every bridge or settlement service used underneath the selected transaction.

The current guide describes a route-selection panel with provider, expected return, fees and estimated arrival time. It also separates the platform charge from a route provider's protocol charge. Inspect both at confirmation rather than inferring total cost from the first displayed token amount.

Use the alternative-route panel

A default selection optimizes according to the interface's criteria. You may have a different operational requirement: a provider your team has already reviewed, a route whose failure handling you understand, or a destination you can actively monitor.

Compare the entire request. Keep source chain, destination chain, both token contracts, amount and recipient unchanged when reviewing alternatives. Otherwise a higher output can simply describe a different asset or transfer.

Recipient settings need deliberate review

KyberSwap documents a separate-recipient option for EVM-to-EVM transfers and different address-entry paths for non-EVM destinations. Do not assume that an address copied from the source wallet is the intended receiving account on every network.

For a third-party recipient, confirm their supported network and exact asset before approval. A route being technically available does not establish that an exchange or service credits that asset at the supplied address.

Define completion before starting

Save the route, expected destination asset and transaction identifiers. A source-chain receipt proves only that the source-side action occurred. Completion means the intended asset arrived at the intended recipient on the intended chain.

If a route fails or pauses, consult the selected provider's applicable process and KyberSwap's tracking details. Do not assume every underlying route shares identical recovery timing just because they are displayed together. The interface unifies discovery; the route still has its own dependencies.