Your Wallet Disconnected After Quote Confirmation. What Now?

If your wallet disconnects after you confirm a quote, the swap’s status is uncertain until you check whether a transaction was signed and broadcast. Confirming a quote usually selects the proposed route and terms; it does not, by itself, prove that your wallet authorized a transaction or that funds moved. The next step is to find the transaction state before you reconnect and try again.

What does quote confirmation mean?

A quote is an estimate of what you may receive along a route, often subject to expiry, fees and changing pool conditions. The wallet’s signature is a separate authorization: depending on the route, you may be asked to approve token spending, sign a swap, or do both. For cross-chain routes, the source-chain transaction can be confirmed before the destination-chain transfer finishes; this account of Biswap’s cross-chain settlement and received output explains that later step in more detail. A wallet disconnect can interrupt the interface without reversing a transaction already submitted to a network.

How can you tell whether the swap went through?

Reconnect to the same wallet and network, then check the activity panel for a transaction hash. If you have one, look it up on the relevant chain’s block explorer and check whether it is pending, confirmed, failed or replaced. For a cross-chain swap, also check the route’s status on the swap interface: source-chain confirmation is not the same as destination-chain completion.

• No signature request completed: the wallet may not have authorized the transaction.
• Signed, but no hash shown: check wallet activity before assuming it was never submitted.
• Hash is pending: wait for its status to resolve; a second submission may create another transaction.
• Source transaction confirmed: check destination settlement and the received token before retrying.

When should you request a new quote?

Request a fresh quote only after you establish that no transaction is still pending and no destination transfer is in progress. A failed source transaction may leave the swap incomplete, while an expired quote can make its original terms unusable; either way, compare the new route and expected output before signing again. If the interface and explorer disagree, use the transaction hash and chain status as your starting point, and contact the service with that hash rather than submitting repeatedly.

The practical rule is simple: quote confirmation describes an offer, while a signed and broadcast transaction creates an on-chain event. Watch the transaction status first, then the destination-chain settlement if the route crosses chains.