Chainflip suits a cross-chain swap when you want a supported asset on its destination chain without receiving a wrapped substitute, and the expected payout meets your needs. After checking both networks and the receiving address, initiate the swap through Chainflip. Compare its expected output and timing with a bridge or custodial exchange before sending funds.
A deposit-channel swap fits when you want to send assets from an ordinary wallet and receive a different asset on another blockchain. For example, you can exchange BTC on Bitcoin for ETH on Ethereum without first acquiring a token that represents BTC. It is less useful when your exact asset pair is unavailable or the quoted payout is poor for your trade size.
The Chainflip exchange supports assets on specific chains, not every token on every network. Its protocol documentation lists BTC on Bitcoin, ETH on Ethereum and Arbitrum, SOL on Solana, and USDC on Ethereum, Arbitrum, Solana and Polkadot Asset Hub. It also lists USDT on several chains, including Tron and BNB Smart Chain. Check the asset and chain together: USDC on Ethereum and USDC on Solana are distinct starting points for a route.
Chainflip uses a broker to register the intended swap on its State Chain and reserve a deposit channel on the source chain. You send the source asset to that channel; validators then confirm the deposit and record it on the State Chain. A just-in-time automated market maker, or JIT AMM, trades against liquidity pools, and the network sends the resulting asset to your destination address. A BTC-to-ETH swap can pass through BTC/USDC and USDC/ETH pools internally without delivering USDC or wrapped BTC to you.
Before sending, compare quotes for the same input amount and destination asset. Look at the amount expected to arrive, the minimum acceptable output if you set one, and the estimated time. The rate can change between the quote and execution; a price limit can prevent an unwanted trade, but a swap that cannot meet it may be refunded with fees deducted.
For a typical cross-chain route, protocol documentation puts the liquidity fee at about 0.10%–0.15% per pool and the network fee at about 0.10%, with a small minimum. You also pay the source-chain transaction cost, while the destination broadcast cost comes out of the payout. A broker may charge a commission, and optional Boost adds roughly 0.05%–0.30% when available. Pool price impact matters too, especially for a large order.
As an illustrative example, suppose you swap $10,000 worth of BTC for ETH at an otherwise unchanged market price. Two pool fees would total roughly $20–$30, and the 0.10% network fee adds about $10: approximately $30–$40 before transaction costs, broker commission, Boost or price impact. Compare the final ETH amount, rather than treating that fee estimate as a guaranteed payout.
Bitcoin confirmation time can be the main wait: the regular route typically requires three blocks, roughly 30 minutes at average block times, before processing and payout. Boost can start processing after one confirmation if enough Boost liquidity is available, for an added fee. An Ethereum deposit has a shorter confirmation window, though the destination transaction still needs to be broadcast.
Keep the deposit-channel details for that swap: channels expire after 24 hours, and an old address may later be reused. Send only through a newly registered swap, and verify the destination and any refund address before transferring funds. A transfer straight to a vault without registered swap instructions may be lost.
A vault swap fits when a wallet or application can build and sign a transaction containing the swap instructions. It sends funds through a vault call instead of waiting for a deposit channel to open. That can remove the channel-opening wait, but the transaction is more complex than a simple wallet transfer and may cost more on the source chain.
Chainflip vault swaps use the same underlying exchange process after validators detect the transaction. They are single-use, so a fresh transaction is needed for another swap. If you are comparing implementations, check whether your wallet supports the required transaction on the source chain, then compare the quoted payout and total source-chain cost with a deposit-channel swap.
A token bridge fits when you want to move exposure to the same asset between chains, rather than trade BTC for ETH or SOL. Some bridges lock a token on one chain and mint a representation on another; others burn and mint an issuer’s token across supported chains. The deciding check is the exact token contract you will receive and whether your destination wallet or application accepts it.
Chainflip swaps are more relevant when the desired output is a different asset on its own chain. A wrapped BTC token on Ethereum, for instance, remains an Ethereum token with a claim on underlying BTC; it is not BTC in a Bitcoin wallet. For a USDC move, compare a bridge’s received token, transfer costs and time with a swap’s final USDC payout on the destination chain.
A custodial exchange fits when you already keep funds there or need an asset pair that a direct cross-chain route does not offer. The process is a deposit, a trade and a withdrawal, with the exchange holding the assets between those steps. Check that it accepts your deposit network and permits withdrawal of the exact asset on the chain you need.
Compare the trade price, trading fee, withdrawal fee, minimum withdrawal and expected release time against the amount a direct swap would deliver. A low trading fee can be offset by a wide spread or costly withdrawal. Custody and any account requirements are also part of the choice.
Before choosing a route, check: