Choose a cross-chain recipient based on what the route will deliver and what the recipient must do next. An address can be syntactically valid while belonging to an account that cannot use the resulting asset or complete the route.
KyberSwap’s cross-chain guide documents recipient choices that vary between EVM and non-EVM destinations. That is a reminder to verify the actual field and destination format rather than assuming the connected source wallet must receive everything.
Three recipient cases
| Recipient | Additional question |
|---|---|
| Your destination wallet | Can it control the account and pay for any later action? |
| Another person’s wallet | Have they confirmed the exact chain and token representation? |
| Exchange or service deposit | Does that service accept this asset, network and transfer method? |
Do not infer deposit acceptance from an address being valid on a chain. A service’s supported deposit rules are separate from a bridge’s ability to send there. If a route requires a memo or other account-specific information that the interface cannot supply, it is not a compatible delivery path.
Look beyond the first arrival
LI.FI’s route documentation includes flows requiring a destination transaction. Sending that intermediate asset to an account you cannot operate can prevent the intended final swap.
Even an automatic route can deliver a fallback asset if destination conversion fails. Check whether the recipient can recognize and use that asset, and which address receives any refund. A different recipient should not leave you assuming recovery always returns to the source wallet.
Review the recipient in the trade form and authorization before committing. If the product does not clearly support the account or delivery requirement, choose a compatible route or arrange a separate transfer after receiving the asset yourself. That adds an explicit step, but keeps the completion responsibility understandable.
Sources & verification (3)
Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.
- Cross-chain Swap
Third-party route aggregation, platform/protocol fee distinction and destination-address choice.
https://docs.kyberswap.com/user-guide/cross-chain-swap - Quote vs Route
Single-step routes and routes requiring a user transaction on the destination chain use different routing constraints.
https://docs.li.fi/introduction/user-flows-and-examples/difference-between-quote-and-route - Intermediate tokens (Why do I received different asset)
When the destination swap cannot complete, the route can deliver a bridged intermediate token and report a partial outcome.
https://help.li.fi/hc/en-us/articles/45779493502747-Intermediate-tokens-Why-do-I-received-different-asset