When a swap starts in a mobile wallet, use the verified app link and check the destination chain and recipient before signing. A deep link hands a request from one app to another; it does not itself move funds or guarantee that every destination detail survived the handoff.
Know what the link carries
- A link opens or resumes an app. It may carry a swap request directly or a session ID that lets the originating service restore it.
- The wallet signs a source-chain transaction. The transaction can include instructions for a bridge and a destination, while the link is only the handoff.
- Review the wallet’s transaction summary. Confirm the source asset, destination network, recipient, and estimated amount before approval.
A deep link may use a custom app scheme or a universal link that opens an app through a web address. Its parameters can include a chain, token, amount, or recipient, but some links carry only a session reference. The app then retrieves the remaining quote. Treat the wallet’s decoded request and transaction summary as the meaningful checks, not the appearance of the URL.
After handoff, the wallet prepares a transaction on the source network. For a cross-chain swap, the signed call can instruct a bridge or messaging layer to deliver funds or a swap instruction to the destination network. The receiving address and destination chain need to remain part of that route; if either is wrong, the source transaction may still succeed while the intended result does not arrive.
Check the destination before signing
For example, suppose you send 0.2 ETH on Ethereum and want USDC on Arbitrum at your own address. Check that the request names Ethereum as the source and Arbitrum as the destination, and that the recipient is your Arbitrum address. The displayed USDC amount is an estimate: fees, execution time, and price movement can change what arrives. Keep enough ETH for source-chain gas as well.
If you are comparing a single cross-chain route with two separate transactions, use when quickswap beats bridge then swap as the decision: compare the expected received amount, number of transactions, and destination control. With quickswap, the service handles moving and swapping assets across chains in one flow; still verify that the quote’s destination matches your intent before you approve the source transaction.
If the wallet opens but the details look incomplete, return to the originating app and recreate the request rather than signing an uncertain transaction. Never enter a recovery phrase into a link or a page opened from one; a legitimate swap request needs transaction approval, not your wallet’s secret recovery words.
Questions to check before your first swap
Does a deep link preserve the destination address?
Only if the request or the restored session includes it and the wallet’s transaction reflects it. Some links carry the full request; others reopen an app that fetches the details again. Compare the recipient shown in the wallet with the address you intended to use. If the wallet does not show enough information to verify the destination, do not sign.
Can I change networks after the link opens?
Switching networks can invalidate a quote or change which transaction the wallet prepares. Return to the swap service, refresh or rebuild the request for the intended source and destination, then inspect the updated summary. I would avoid changing networks mid-request because a stale quote can show details that no longer match the transaction being signed.
- Open the verified app link and confirm the source network.
- Check destination network, asset, recipient, and estimated amount in the wallet.
- Keep source-chain gas available, then sign only after the details match.
Top comments (0)