The default input is BTC on Bitcoin; the output is LTC on Litecoin. Change either network in the app before requesting a quote if your wallet needs another supported version.
Swap BTC to LTC
Change on-chain BTC into native Litecoin when the recipient or next payment specifically requires LTC. Compare the final Litecoin output with the actual Bitcoin amount that will leave your sending wallet.
Pay with BTC on Bitcoin
Route, cost, and recovery details
Non-confidential crypto swaps have a 0.5% uSwap platform fee, waived every weekend (UTC). The amount received can still reflect provider pricing or spread, blockchain network costs, market movement, and any selected confidential, fast, fiat, or affiliate fee. The quote displays the modeled breakdown before funds are sent. Floating or expired quotes may be recalculated.
Eligibility, verification requirements, transaction limits, sanctions controls, and geographic restrictions can vary by the selected route, provider, counterparty, and destination product.
uSwap does not provide users with a wallet account or an ongoing stored balance. Depending on the selected route, funds may be sent directly to a provider or may temporarily enter an address or balance controlled by a provider, uSwap automation, or an operator for execution, settlement, or recovery.
uSwap selects the best-scoring eligible route returned by the enabled providers for the selected assets and settings. This is not a guarantee of the best price across every market.
uSwap automates common underpayment, overpayment, late-deposit, re-quote, and refund cases. Some wrong-asset, wrong-network, provider-ambiguous, already-broadcast, or unsupported-token cases may require provider or operator review and may not be recoverable. Timing and deductions depend on the route, provider, and network.
Bitcoin to Litecoin: what changes
Change on-chain BTC into native Litecoin when the recipient or next payment specifically requires LTC. Compare the final Litecoin output with the actual Bitcoin amount that will leave your sending wallet.
| Check | Sending side | Receiving side |
|---|---|---|
| Asset | BTC | LTC |
| Network | Bitcoin | Litecoin |
| Normal wallet gas | BTC | LTC for later outgoing transfers |
| Instructions | The bridge’s current deposit details | Your own receiving wallet or exchange details |
Before sending BTC
Use a Bitcoin on-chain withdrawal, not a Lightning invoice or a wrapped-BTC token. The sending wallet decides the transaction fee; a low-fee transaction can remain unconfirmed before the swap has any funds to use.
If you withdraw from an exchange, compare its final withdrawal amount with the bridge instructions. A platform withdrawal charge and the swap’s modeled costs are separate. Do not send a token or choose a network merely because the address format looks compatible.
Receiving LTC
Use an address supplied by the Litecoin receiving wallet or exchange. Check that it is intended for native LTC. An address error cannot be fixed by changing the bridge after a destination transfer has already been broadcast.
Check the final wallet or exchange deposit screen before creating the bridge. If it asks for a memo or tag, include it in the appropriate destination field. The sending transaction and destination transaction are separate; save the bridge link to follow both.
Request the route and review the cost
- Open the preselected BTC → LTC route above. Confirm both networks.
- Enter the input amount and your receiving details.
- Compare the modeled LTC output, quote type, costs, and any available timing estimate.
- Create the bridge and send only according to its current instructions.
- Return to that bridge to track confirmations, execution, and delivery.
A route may use several steps even though you see one final output. Availability and limits come from the live quote, not a permanent minimum or conversion rate on this page. See how bridges work for endpoints, deposits, intents, and holds.
If the deposit or payout is missing
First check that the wallet actually broadcast the Bitcoin transaction. Then compare its address, asset, network, and net amount with the saved bridge. If the bridge detected the deposit, read its current stage before sending more funds.
For a hold, expired quote, or refund request, use the action on the original bridge. Recovery depends on the network, provider, and state of the funds; it is not guaranteed. The troubleshooting guide explains what to check and which details to keep.