What is bridge and cross-chain swap?
Cross-chain actions allow users to move or exchange assets across different blockchains. In KuCoin Web3 Wallet, this can happen through cross-chain swaps or bridging. While both involve multiple networks, they serve different purposes and follow different execution paths. Understanding how they work helps you set correct expectations around timing, fees, and transaction status.
1. What Is a Bridge?
A bridge transfers the same asset from one blockchain to another.
Example:
USDC on Ethereum → USDC on Arbitrum
What happens behind the scenes:
- Assets are locked or burned on the source chain
- Equivalent assets are minted or released on the destination chain
- The process may rely on relayers, validators, or liquidity pools
Because this involves multiple confirmations and off-chain coordination, bridging is not always instant.
2. What Is a Cross-chain Swap?
A cross-chain swap exchanges one asset on one chain for another asset on a different chain.
Example:
ETH (Ethereum) → SOL (Solana)
A cross-chain swap usually includes:
- A swap on the source chain
- A bridge transaction
- A swap on the destination chain
Although this appears as one action in the wallet UI, it is actually a multi-step process executed through aggregators and liquidity providers.
3. Why Cross-chain Actions Take Time
Cross-chain transactions may take longer due to:
- Network congestion on either chain
- Bridge liquidity availability
- Relayer processing delays
- Security confirmation windows
A transaction confirmed on the source chain does not mean it has finalized on the destination chain.
4. Fees Involved
Cross-chain actions may include:
- Source chain gas fees
- Bridge protocol fees
- Destination chain gas fees
- Swap price impact or slippage
These fees are bundled in the quoted estimate before you confirm the transaction.
5. Important Things to Know
- Cross-chain swaps involve multiple protocols, not a single transaction
- Delays do not always indicate failure
- Funds are not lost simply because a transfer is taking longer
- Retrying too early may cause duplicate transactions
If a transaction remains pending for an unusually long time, check the transaction hash on both chains before taking action.