On AllSwap, a cross-chain swap converts an asset on a source blockchain and settles the result on a different destination chain. A same-chain swap only exchanges tokens within one network. The defining difference is whether the funds cross a blockchain boundary, which changes the liquidity, process, timing, costs, and risks. Choose based on the network you actually need, not merely the token name.
How are cross-chain and same-chain swaps different?
In a same-chain swap, the input and output assets are on the same blockchain. For example, a user may exchange ETH for USDC on Ethereum through a decentralized exchange or an aggregator on that chain. The wallet signs on one network, and any token approval, trade execution, and final confirmation all occur on that network. No second blockchain needs to reach finality.
A cross-chain swap involves at least a source chain and a destination chain. Examples include spending BTC on the Bitcoin network to receive USDT on the TRON network, or converting USDC on Ethereum into USDC on Solana. The first example changes both the network and the asset; the second mainly changes where the asset exists. Both are cross-chain transactions. Assets on each chain have their own on-chain identifiers—for example, a contract address on an EVM network or a mint address on Solana—so assets with the same ticker should not be treated as the same on-chain object. Their risk profiles may also differ.
| Comparison | Same-chain swap | Cross-chain swap |
|---|---|---|
| Network scope | Input and output are on one chain | Input and output are on different chains |
| Liquidity source | Primarily an on-chain pool or market maker on that network | Requires coordinated liquidity and settlement across the source and destination chains |
| Typical interaction | Connect a wallet, approve a token, and sign a transaction | May use a bridge, cross-chain protocol, or one-time deposit address |
| Completion time | Usually depends on block production and congestion on one chain | Also depends on source-chain confirmation, route execution, and destination-chain settlement |
| Cost components | Network gas, trading fees, and price impact | Source-chain gas, cross-chain settlement costs, liquidity spread, service fees, and other applicable costs |
| Main risks | Slippage, malicious tokens, smart-contract risk, or pool liquidity risk | Also includes cross-chain protocol risk, conditions on two networks, and wrong-network errors |
How does AllSwap complete a cross-chain swap?
The AllSwap cross-chain swap page uses a non-custodial aggregation model. First, the user selects the source-chain asset, destination-chain asset, and amount. During setup, the interface shows a preview based on current liquidity. The user then enters a destination-chain recipient address and, optionally, a source-chain refund address. Only after that does the system request a firm quote and create an order.
Once the order has been created, the payment page displays the final estimated amount to receive, minimum amount to receive, the effect of fees, one-time deposit address, and payment countdown. If the source-chain deposit requires additional identifying information, the order also provides a deposit Memo or Tag for the payment side. A preview is not a confirmed order and does not replace the final figures and instructions on the payment page.
The user must send the exact asset and amount shown on the page, in a single payment, from the correct source network to the specified deposit address. AllSwap detects the deposit and waits for the required blockchain confirmations. The underlying settlement network then executes the exchange and sends the destination asset to the address provided by the user. The user can check the order status and on-chain transaction hashes to verify progress and completion. AllSwap is not a wallet or centralized exchange, and this process does not normally require the user to create an account, connect a wallet, or give AllSwap permission to operate their tokens.
“Cross-chain aggregation” does not mean that AllSwap itself is a single standalone bridge. A single bridge generally focuses on moving particular assets—or bridged representations of those assets—to another chain. An aggregation service compares the available quotes and settlement routes at that time, then presents route selection as one exchange flow. However, the appearance of a pair in an interface does not mean every asset, network, amount, and direction will always have liquidity. Actual availability depends on whether the page can return a valid live quote.
When should you use a same-chain swap or a cross-chain swap?
If your funds are already on the destination blockchain and you only want another token on that same chain, a same-chain swap will usually involve fewer steps and be easier to verify in a block explorer. For example, if you hold SOL on Solana and want USDC on Solana, there is no need to move the funds to another network first.
A cross-chain swap is more suitable when the asset you need is on another chain, or when you need funds in another ecosystem—for example, to pay gas on the destination chain, use an application there, or transfer assets to a wallet that supports that network. Combining the bridge and swap into one route may reduce the work of switching networks manually, finding destination-chain gas, and comparing several protocols separately. It is not necessarily cheaper in every case: the outcome still depends on live liquidity, the amount, and network conditions.
Before deciding, check the following in order:
- Confirm the exact destination network you need, not just the token ticker. USDT, USDC, and other similarly named assets have different on-chain identifiers across networks, such as an EVM contract address or a Solana mint address.
- Confirm that the recipient wallet or platform supports both the destination network and the exact asset identifier. The currently documented AllSwap flow only confirms that an order may provide a deposit Memo or Tag for the payment side. If an exchange deposit address on the destination chain requires a recipient-side Memo or Tag but the AllSwap order page has no field for it, do not use that address directly. Receive the funds in a self-custody wallet that supports the destination network first.
- Compare the final “minimum received” amount rather than only the displayed exchange rate. Include source-chain gas and any withdrawal fee charged by another platform in the total cost. See the AllSwap fee explanation for the applicable cost boundaries.
- Check the order's payment countdown and estimated processing time. A cross-chain swap must wait for source-chain confirmation and destination-chain settlement, so it should not be judged by the expected speed of a same-chain swap.
- Prefer paying from a self-custody wallet that you control. Enter a source-chain refund address that you control when creating the order, and save the order ID, deposit address, transaction hash, and payment record.
What additional risks come with a cross-chain swap?
A cross-chain swap is not simply a same-chain transaction copied onto another network. Source-chain congestion, a block reorganization, a destination-chain pause, changing liquidity, or an issue in the underlying settlement process can delay an order or move it into a refund or manual-review workflow. Rapid market movement can also prevent a transaction from completing through its original route when it moves outside the order's protection range. The displayed processing time is therefore an estimate, while the quote and payment deadline should always be taken from the current order.
The most serious common mistakes are selecting the wrong network, sending the wrong token, omitting a required deposit Memo, or sending funds to an old deposit address after it has expired. Blockchain transfers are generally irreversible, and AllSwap cannot guarantee that an incorrect transfer can be recovered. Before paying, verify the source network, asset, amount, deposit address, and payment-side Memo character by character. Also confirm that the receiving wallet supports the destination chain. If the receiving platform separately requires a recipient-side Memo, apply the compatibility rule explained above. If funds have not arrived, do not make another payment to the same address. First confirm the source-chain transaction in a block explorer, then follow the guidance in the AllSwap Help Center.
The refund path also requires special attention. If a refund address was entered in the order, a failed order is refunded to that designated address. If the user did not enter a refund address, a refund required by an exception is first sent to AllSwap's platform fallback refund address. The user must then contact official support and provide authentic proof of payment. An agent can process a manual refund only after verifying both the order and ownership of the payment. Paying from an exchange or custodial wallet may make ownership harder to prove. Accordingly, “non-custodial” does not mean that every mistake can be recovered automatically, and a cross-chain swap should not be treated as a risk-free transfer.