Compare connected-wallet and deposit-based crypto swap workflows, destination-wallet requirements, no-wallet-connect route limits, and direct-transfer claims.
Wallet connection
Route-dependent
Some routes connect a wallet; others use deposit instructions.
Quote comparison
Can precede execution
Route discovery and signing are separate stages.
Direct transfer claim
Not assumed
Provider paths can include multiple steps.
Destination wallet
Must be compatible
Verify the exact network and asset representation.
A route can begin from one wallet and deliver to another, but the path may include contracts, bridges, exchanges, solvers, liquidity, or a provider deposit address. “Wallet-to-wallet” does not necessarily mean one direct on-chain transfer.
Some routes use a wallet connection to read the source address, prepare approvals, switch networks, sign transactions, or track execution. Connecting a wallet does not give the site a seed phrase or private key.
Some Sasquatch route modes can use manual deposit instructions and a receiving address without connecting a wallet to the interface. Availability is route-specific, and a compatible source wallet is still needed to send the deposit.
The route API can compare paths without configuring an execution wallet. Executing a selected path can later require signing, a manual transfer, or another route-specific step.
Do not assume a direct wallet-to-wallet transfer. The exact provider path may include multiple steps or counterparties even when the user experience starts and ends with wallet addresses.
Verify destination network, address format, memo or tag, token representation, provider, amount, output, fees, and quote window. A wrong destination can be unrecoverable.
It describes a workflow that starts from a source wallet and delivers to a receiving wallet, but the provider path can include contracts, bridges, exchanges, solvers, or deposit instructions.
Yes. Route comparison can occur before execution. A selected route may later require signing or a manual wallet transfer.
Some routes may use manual deposit instructions instead of a connected-wallet flow. Check the exact live route requirements.
Not necessarily. Use “direct” only when the displayed provider path confirms it.
